User interfaces for managing locks

ABSTRACT

The present disclosure generally relates to user interfaces for managing locks. In some examples, an electronic device displays user interfaces for configuring a lock accessory device based on detected features of the lock accessory device, such as a short-range communication user interface for enabling an express mode of the lock accessory device and/or a pin user interface object for enabling a code for accessing the lock accessory device. In some examples, an electronic device displays a user interface corresponding to a respective user of a home automation system that includes statuses indicating whether the respective user has access to a plurality of lock accessory devices of the home automation system.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.17/484,469, filed on Sep. 24, 2021, entitled “USER INTERFACES FORMANAGING LOCKS,” which claims benefit to U.S. Provisional ApplicationNo. 63/197,462, filed Jun. 6, 2021, entitled “USER INTERFACES FORMANAGING LOCKS,” the entire contents of each of which are herebyincorporated by reference in their entirety.

FIELD

The present disclosure relates generally to computer user interfaces,and more specifically to techniques for managing lock accessories.

BACKGROUND

Electronic devices are able to wirelessly communicate with a lockaccessory to cause the lock accessory to transition between a lockedstate and an unlocked state while displaying a user interfacecorresponding to the lock accessory. Electronic devices can alsocommunicate with a lock accessory to set a personal identificationnumber (PIN) that can be used to cause the lock accessory to transitionbetween the locked state and the unlocked state via inputs on a keypadof the lock accessory.

BRIEF SUMMARY

Some techniques for managing lock accessories using electronic devices,however, are generally cumbersome and inefficient. For example, someexisting techniques use a complex and time-consuming user interface,which may include multiple key presses or keystrokes. Existingtechniques require more time than necessary, wasting user time anddevice energy. This latter consideration is particularly important inbattery-operated devices.

Accordingly, the present technique provides electronic devices withfaster, more efficient methods and interfaces for managing lockaccessories. Such methods and interfaces optionally complement orreplace other methods for managing lock accessories. Such methods andinterfaces reduce the cognitive burden on a user and produce a moreefficient human-machine interface. For example, such methods andinterfaces facilitate a setup process for establishing communicationbetween an electronic device and a lock accessory. As another example,such methods and interfaces enable a user to quickly and efficientlymanage access to multiple lock accessories for guests and/or otherusers. For battery-operated computing devices, such methods andinterfaces conserve power and increase the time between battery charges.

In accordance with some embodiments, a method is described. The methodis performed at a computer system that is in communication with adisplay generation component and one or more input devices. The methodcomprises: receiving, via the one or more input devices, a request toconfigure an electronic lock that is separate from the computer system;in response to receiving the request to configure the electronic lock,starting a configuration process for configuring the electronic lock;and during the configuration process for configuring the electroniclock: in accordance with a determination that the electronic lockincludes a short-range communication feature for communicating viashort-range wireless communication, displaying, via the displaygeneration component, an option to configure a first account of thecomputer system to provide credentials via short-range communicationwithout requiring authentication; in accordance with a determinationthat the electronic lock does not include the short-range communicationfeature, forgoing display, via the display generation component, of theoption to configure the first account of the computer system to providecredentials without requiring authentication; in accordance with adetermination that the electronic lock includes a keypad feature,displaying, via the display generation component, an option to configurea code of the first account of the computer system to be used forunlocking the electronic lock via the keypad feature of the electroniclock; and in accordance with a determination that the electronic lockdoes not include the keypad feature, forgoing display, via the displaygeneration component, of the option to configure a code of the firstaccount of the computer system to be used for unlocking the electroniclock.

In accordance with some embodiments, a non-transitory computer-readablestorage medium is described. The non-transitory computer-readablestorage medium stores one or more programs configured to be executed byone or more processors of a computer system that is in communicationwith a display generation component and one or more input devices, theone or more programs including instructions for: receiving, via the oneor more input devices, a request to configure an electronic lock that isseparate from the computer system; in response to receiving the requestto configure the electronic lock, starting a configuration process forconfiguring the electronic lock; and during the configuration processfor configuring the electronic lock: in accordance with a determinationthat the electronic lock includes a short-range communication featurefor communicating via short-range wireless communication, displaying,via the display generation component, an option to configure a firstaccount of the computer system to provide credentials via short-rangecommunication without requiring authentication; in accordance with adetermination that the electronic lock does not include the short-rangecommunication feature, forgoing display, via the display generationcomponent, of the option to configure the first account of the computersystem to provide credentials without requiring authentication; inaccordance with a determination that the electronic lock includes akeypad feature, displaying, via the display generation component, anoption to configure a code of the first account of the computer systemto be used for unlocking the electronic lock via the keypad feature ofthe electronic lock; and in accordance with a determination that theelectronic lock does not include the keypad feature, forgoing display,via the display generation component, of the option to configure a codeof the first account of the computer system to be used for unlocking theelectronic lock.

In accordance with some embodiments, a transitory computer-readablestorage medium is described. The transitory computer-readable storagemedium stores one or more programs configured to be executed by one ormore processors of a computer system that is in communication with adisplay generation component and one or more input devices, the one ormore programs including instructions for: receiving, via the one or moreinput devices, a request to configure an electronic lock that isseparate from the computer system; in response to receiving the requestto configure the electronic lock, starting a configuration process forconfiguring the electronic lock; and during the configuration processfor configuring the electronic lock: in accordance with a determinationthat the electronic lock includes a short-range communication featurefor communicating via short-range wireless communication, displaying,via the display generation component, an option to configure a firstaccount of the computer system to provide credentials via short-rangecommunication without requiring authentication; in accordance with adetermination that the electronic lock does not include the short-rangecommunication feature, forgoing display, via the display generationcomponent, of the option to configure the first account of the computersystem to provide credentials without requiring authentication; inaccordance with a determination that the electronic lock includes akeypad feature, displaying, via the display generation component, anoption to configure a code of the first account of the computer systemto be used for unlocking the electronic lock via the keypad feature ofthe electronic lock; and in accordance with a determination that theelectronic lock does not include the keypad feature, forgoing display,via the display generation component, of the option to configure a codeof the first account of the computer system to be used for unlocking theelectronic lock.

In accordance with some embodiments, a computer system is described. Thecomputer system is configured to communicate with a display generationcomponent and one or more input devices. The computer system comprises:one or more processors; and memory storing one or more programsconfigured to be executed by the one or more processors, the one or moreprograms including instructions for: receiving, via the one or moreinput devices, a request to configure an electronic lock that isseparate from the computer system; in response to receiving the requestto configure the electronic lock, starting a configuration process forconfiguring the electronic lock; and during the configuration processfor configuring the electronic lock: in accordance with a determinationthat the electronic lock includes a short-range communication featurefor communicating via short-range wireless communication, displaying,via the display generation component, an option to configure a firstaccount of the computer system to provide credentials via short-rangecommunication without requiring authentication; in accordance with adetermination that the electronic lock does not include the short-rangecommunication feature, forgoing display, via the display generationcomponent, of the option to configure the first account of the computersystem to provide credentials without requiring authentication; inaccordance with a determination that the electronic lock includes akeypad feature, displaying, via the display generation component, anoption to configure a code of the first account of the computer systemto be used for unlocking the electronic lock via the keypad feature ofthe electronic lock; and in accordance with a determination that theelectronic lock does not include the keypad feature, forgoing display,via the display generation component, of the option to configure a codeof the first account of the computer system to be used for unlocking theelectronic lock.

In accordance with some embodiments, a computer system is described. Thecomputer system is configured to communicate with a display generationcomponent and one or more input devices. The computer system comprises:means for receiving, via the one or more input devices, a request toconfigure an electronic lock that is separate from the computer system;means for, in response to receiving the request to configure theelectronic lock, starting a configuration process for configuring theelectronic lock; and means for, during the configuration process forconfiguring the electronic lock: in accordance with a determination thatthe electronic lock includes a short-range communication feature forcommunicating via short-range wireless communication, displaying, viathe display generation component, an option to configure a first accountof the computer system to provide credentials via short-rangecommunication without requiring authentication; in accordance with adetermination that the electronic lock does not include the short-rangecommunication feature, forgoing display, via the display generationcomponent, of the option to configure the first account of the computersystem to provide credentials without requiring authentication; inaccordance with a determination that the electronic lock includes akeypad feature, displaying, via the display generation component, anoption to configure a code of the first account of the computer systemto be used for unlocking the electronic lock via the keypad feature ofthe electronic lock; and in accordance with a determination that theelectronic lock does not include the keypad feature, forgoing display,via the display generation component, of the option to configure a codeof the first account of the computer system to be used for unlocking theelectronic lock.

In accordance with some embodiments, a computer program product isdescribed. The computer program product comprises one or more programsconfigured to be executed by one or more processors of a computer systemthat is in communication with a display generation component and one ormore input devices, the one or more programs including instructions for:receiving, via the one or more input devices, a request to configure anelectronic lock that is separate from the computer system; in responseto receiving the request to configure the electronic lock, starting aconfiguration process for configuring the electronic lock; and duringthe configuration process for configuring the electronic lock: inaccordance with a determination that the electronic lock includes ashort-range communication feature for communicating via short-rangewireless communication, displaying, via the display generationcomponent, an option to configure a first account of the computer systemto provide credentials via short-range communication without requiringauthentication; in accordance with a determination that the electroniclock does not include the short-range communication feature, forgoingdisplay, via the display generation component, of the option toconfigure the first account of the computer system to providecredentials without requiring authentication; in accordance with adetermination that the electronic lock includes a keypad feature,displaying, via the display generation component, an option to configurea code of the first account of the computer system to be used forunlocking the electronic lock via the keypad feature of the electroniclock; and in accordance with a determination that the electronic lockdoes not include the keypad feature, forgoing display, via the displaygeneration component, of the option to configure a code of the firstaccount of the computer system to be used for unlocking the electroniclock.

In accordance with some embodiments, a method is described. The methodis performed at a computer system that is in communication with adisplay generation component and one or more input devices. The methodcomprises: displaying, via the display generation component, an accountuser interface that includes a user account lock object; whiledisplaying the user account lock object, receiving, via the one or moreinput devices, a first input corresponding to selection of the useraccount lock object; and in response to receiving the first input,displaying, via the display generation component, a user account lockuser interface corresponding to a first account, wherein the useraccount lock user interface includes concurrent display of: a firstelectronic lock object corresponding to a first electronic lock that isseparate from the computer system; a first status object that indicateswhether the first electronic lock is configured to unlock usingcredentials of the first account; a second electronic lock objectcorresponding to a second electronic lock that is separate from thecomputer system; and a second status object that indicates whether thesecond electronic lock is configured to unlock using credentials of thefirst account.

In accordance with some embodiments, a non-transitory computer-readablestorage medium is described. The non-transitory computer-readablestorage medium stores one or more programs configured to be executed byone or more processors of a computer system that is in communicationwith a display generation component and one or more input devices, theone or more programs including instructions for: displaying, via thedisplay generation component, an account user interface that includes auser account lock object; while displaying the user account lock object,receiving, via the one or more input devices, a first inputcorresponding to selection of the user account lock object; and inresponse to receiving the first input, displaying, via the displaygeneration component, a user account lock user interface correspondingto a first account, wherein the user account lock user interfaceincludes concurrent display of: a first electronic lock objectcorresponding to a first electronic lock that is separate from thecomputer system; a first status object that indicates whether the firstelectronic lock is configured to unlock using credentials of the firstaccount; a second electronic lock object corresponding to a secondelectronic lock that is separate from the computer system; and a secondstatus object that indicates whether the second electronic lock isconfigured to unlock using credentials of the first account.

In accordance with some embodiments, a transitory computer-readablestorage medium is described. The transitory computer-readable storagemedium stores one or more programs configured to be executed by one ormore processors of a computer system that is in communication with adisplay generation component and one or more input devices, the one ormore programs including instructions for: displaying, via the displaygeneration component, an account user interface that includes a useraccount lock object; while displaying the user account lock object,receiving, via the one or more input devices, a first inputcorresponding to selection of the user account lock object; and inresponse to receiving the first input, displaying, via the displaygeneration component, a user account lock user interface correspondingto a first account, wherein the user account lock user interfaceincludes concurrent display of: a first electronic lock objectcorresponding to a first electronic lock that is separate from thecomputer system; a first status object that indicates whether the firstelectronic lock is configured to unlock using credentials of the firstaccount; a second electronic lock object corresponding to a secondelectronic lock that is separate from the computer system; and a secondstatus object that indicates whether the second electronic lock isconfigured to unlock using credentials of the first account.

In accordance with some embodiments, a computer system is described. Thecomputer system is configured to communicate with a display generationcomponent and one or more input devices. The computer system comprises:one or more processors; and memory storing one or more programsconfigured to be executed by the one or more processors, the one or moreprograms including instructions for: displaying, via the displaygeneration component, an account user interface that includes a useraccount lock object; while displaying the user account lock object,receiving, via the one or more input devices, a first inputcorresponding to selection of the user account lock object; and inresponse to receiving the first input, displaying, via the displaygeneration component, a user account lock user interface correspondingto a first account, wherein the user account lock user interfaceincludes concurrent display of: a first electronic lock objectcorresponding to a first electronic lock that is separate from thecomputer system; a first status object that indicates whether the firstelectronic lock is configured to unlock using credentials of the firstaccount; a second electronic lock object corresponding to a secondelectronic lock that is separate from the computer system; and a secondstatus object that indicates whether the second electronic lock isconfigured to unlock using credentials of the first account.

In accordance with some embodiments, a computer system is described. Thecomputer system is configured to communicate with a display generationcomponent and one or more input devices. The computer system comprises:means for displaying, via the display generation component, an accountuser interface that includes a user account lock object; means for,while displaying the user account lock object, receiving, via the one ormore input devices, a first input corresponding to selection of the useraccount lock object; and means for, in response to receiving the firstinput, displaying, via the display generation component, a user accountlock user interface corresponding to a first account, wherein the useraccount lock user interface includes concurrent display of: a firstelectronic lock object corresponding to a first electronic lock that isseparate from the computer system; a first status object that indicateswhether the first electronic lock is configured to unlock usingcredentials of the first account; a second electronic lock objectcorresponding to a second electronic lock that is separate from thecomputer system; and a second status object that indicates whether thesecond electronic lock is configured to unlock using credentials of thefirst account.

In accordance with some embodiments, a computer program product isdescribed. The computer program product comprises one or more programsconfigured to be executed by one or more processors of a computer systemthat is in communication with a display generation component and one ormore input devices, the one or more programs including instructions for:displaying, via the display generation component, an account userinterface that includes a user account lock object; while displaying theuser account lock object, receiving, via the one or more input devices,a first input corresponding to selection of the user account lockobject; and in response to receiving the first input, displaying, viathe display generation component, a user account lock user interfacecorresponding to a first account, wherein the user account lock userinterface includes concurrent display of: a first electronic lock objectcorresponding to a first electronic lock that is separate from thecomputer system; a first status object that indicates whether the firstelectronic lock is configured to unlock using credentials of the firstaccount; a second electronic lock object corresponding to a secondelectronic lock that is separate from the computer system; and a secondstatus object that indicates whether the second electronic lock isconfigured to unlock using credentials of the first account.

Executable instructions for performing these functions are, optionally,included in a non-transitory computer-readable storage medium or othercomputer program product configured for execution by one or moreprocessors. Executable instructions for performing these functions are,optionally, included in a transitory computer-readable storage medium orother computer program product configured for execution by one or moreprocessors.

Thus, devices are provided with faster, more efficient methods andinterfaces for managing lock accessories, thereby increasing theeffectiveness, efficiency, and user satisfaction with such devices. Suchmethods and interfaces may complement or replace other methods formanaging lock accessories.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIGS. 6A-6V illustrate exemplary user interfaces for configuring and/orusing a lock accessory, in accordance with some embodiments.

FIG. 7 is a flow diagram illustrating a method for configuring a lockaccessory, in accordance with some embodiments.

FIGS. 8A-8S illustrate exemplary user interfaces for managing access forone or more lock accessories, in accordance with some embodiments.

FIG. 9 is a flow diagram illustrating a method for managing access forone or more lock accessories, in accordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

There is a need for electronic devices that provide efficient methodsand interfaces for managing lock accessories. For example, there is aneed for electronic devices that facilitate a setup process forconfiguring a lock accessory based on features of the lock accessory. Asanother example, there a need for electronic devices that enable a userto quickly and efficiently manage access to one or more lock accessoriesfor guests and/or users. Such techniques can reduce the cognitive burdenon a user who manages lock accessories, thereby enhancing productivity.Further, such techniques can reduce processor and battery powerotherwise wasted on redundant user inputs.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5B provide a description ofexemplary devices for performing the techniques for managing lockaccessories. FIGS. 6A-6V illustrate exemplary user interfaces forconfiguring and/or using a lock accessory. FIG. 7 is a flow diagramillustrating methods for configuring a lock accessory in accordance withsome embodiments. The user interfaces in FIGS. 6A-6V are used toillustrate the processes described below, including the processes inFIG. 7 . FIGS. 8A-8S illustrate exemplary user interfaces for managingaccess for one or more lock accessories. FIG. 9 is a flow diagramillustrating methods for managing access for one or more lockaccessories in accordance with some embodiments. The user interfaces inFIGS. 8A-8S are used to illustrate the processes described below,including the processes in FIG. 9 .

In addition, in methods described herein where one or more steps arecontingent upon one or more conditions having been met, it should beunderstood that the described method can be repeated in multiplerepetitions so that over the course of the repetitions all of theconditions upon which steps in the method are contingent have been metin different repetitions of the method. For example, if a methodrequires performing a first step if a condition is satisfied, and asecond step if the condition is not satisfied, then a person of ordinaryskill would appreciate that the claimed steps are repeated until thecondition has been both satisfied and not satisfied, in no particularorder. Thus, a method described with one or more steps that arecontingent upon one or more conditions having been met could berewritten as a method that is repeated until each of the conditionsdescribed in the method has been met. This, however, is not required ofsystem or computer readable medium claims where the system or computerreadable medium contains instructions for performing the contingentoperations based on the satisfaction of the corresponding one or moreconditions and thus is capable of determining whether the contingencyhas or has not been satisfied without explicitly repeating steps of amethod until all of the conditions upon which steps in the method arecontingent have been met. A person having ordinary skill in the artwould also understand that, similar to a method with contingent steps, asystem or computer readable storage medium can repeat the steps of amethod as many times as are needed to ensure that all of the contingentsteps have been performed.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. In some embodiments, these terms are used to distinguish oneelement from another. For example, a first touch could be termed asecond touch, and, similarly, a second touch could be termed a firsttouch, without departing from the scope of the various describedembodiments. In some embodiments, the first touch and the second touchare two separate references to the same touch. In some embodiments, thefirst touch and the second touch are both touches, but they are not thesame touch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” is, optionally, construed to mean “when” or “upon” or “inresponse to determining” or “in response to detecting,” depending on thecontext. Similarly, the phrase “if it is determined” or “if [a statedcondition or event] is detected” is, optionally, construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad). In some embodiments, the electronic deviceis a computer system that is in communication (e.g., via wirelesscommunication, via wired communication) with a display generationcomponent. The display generation component is configured to providevisual output, such as display via a CRT display, display via an LEDdisplay, or display via image projection. In some embodiments, thedisplay generation component is integrated with the computer system. Insome embodiments, the display generation component is separate from thecomputer system. As used herein, “displaying” content includes causingto display the content (e.g., video data rendered or decoded by displaycontroller 156) by transmitting, via a wired or wireless connection,data (e.g., image data or video data) to an integrated or externaldisplay generation component to visually produce the content.

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Memory controller 122optionally controls access to memory 102 by other components of device100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs (such ascomputer programs (e.g., including instructions)) and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 are, optionally,implemented on a single chip, such as chip 104. In some otherembodiments, they are, optionally, implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2 ). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, depth camera controller 169,intensity sensor controller 159, haptic feedback controller 161, and oneor more input controllers 160 for other input or control devices. Theone or more input controllers 160 receive/send electrical signalsfrom/to other input control devices 116. The other input control devices116 optionally include physical buttons (e.g., push buttons, rockerbuttons, etc.), dials, slider switches, joysticks, click wheels, and soforth. In some embodiments, input controller(s) 160 are, optionally,coupled to any (or none) of the following: a keyboard, an infrared port,a USB port, and a pointer device such as a mouse. The one or morebuttons (e.g., 208, FIG. 2 ) optionally include an up/down button forvolume control of speaker 111 and/or microphone 113. The one or morebuttons optionally include a push button (e.g., 206, FIG. 2 ). In someembodiments, the electronic device is a computer system that is incommunication (e.g., via wireless communication, via wiredcommunication) with one or more input devices. In some embodiments, theone or more input devices include a touch-sensitive surface (e.g., atrackpad, as part of a touch-sensitive display). In some embodiments,the one or more input devices include one or more camera sensors (e.g.,one or more optical sensors 164 and/or one or more depth camera sensors175), such as for tracking a user's gestures (e.g., hand gestures)and/or air gestures) as input. In some embodiments, the one or moreinput devices are integrated with the computer system. In someembodiments, the one or more input devices are separate from thecomputer system. In some embodiments, an air gesture is a gesture thatis detected without the user touching an input element that is part ofthe device (or independently of an input element that is a part of thedevice) and is based on detected motion of a portion of the user's bodythrough the air including motion of the user's body relative to anabsolute reference (e.g., an angle of the user's arm relative to theground or a distance of the user's hand relative to the ground),relative to another portion of the user's body (e.g., movement of a handof the user relative to a shoulder of the user, movement of one hand ofthe user relative to another hand of the user, and/or movement of afinger of the user relative to another finger or portion of a hand ofthe user), and/or absolute motion of a portion of the user's body (e.g.,a tap gesture that includes movement of a hand in a predetermined poseby a predetermined amount and/or speed, or a shake gesture that includesa predetermined speed or amount of rotation of a portion of the user'sbody).

A quick press of the push button optionally disengages a lock of touchscreen 112 or optionally begins a process that uses gestures on thetouch screen to unlock the device, as described in U.S. patentapplication Ser. No. 11/322,549, “Unlocking a Device by PerformingGestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No.7,657,849, which is hereby incorporated by reference in its entirety. Alonger press of the push button (e.g., 206) optionally turns power todevice 100 on or off. The functionality of one or more of the buttonsare, optionally, user-customizable. Touch screen 112 is used toimplement virtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output optionally corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other embodiments. Touch screen 112 and display controller156 optionally detect contact and any movement or breaking thereof usingany of a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 112. In an exemplary embodiment, projectedmutual capacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 is,optionally, analogous to the multi-touch sensitive touchpads describedin the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat.No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 isdescribed in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 optionally has a video resolution in excess of 100 dpi.In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad is, optionally, a touch-sensitive surface that isseparate from touch screen 112 or an extension of the touch-sensitivesurface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 optionally includescharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 optionallycaptures still images or video. In some embodiments, an optical sensoris located on the back of device 100, opposite touch screen display 112on the front of the device so that the touch screen display is enabledfor use as a viewfinder for still and/or video image acquisition. Insome embodiments, an optical sensor is located on the front of thedevice so that the user's image is, optionally, obtained for videoconferencing while the user views the other video conferenceparticipants on the touch screen display. In some embodiments, theposition of optical sensor 164 can be changed by the user (e.g., byrotating the lens and the sensor in the device housing) so that a singleoptical sensor 164 is used along with the touch screen display for bothvideo conferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more depth camera sensors175. FIG. 1A shows a depth camera sensor coupled to depth cameracontroller 169 in I/O subsystem 106. Depth camera sensor 175 receivesdata from the environment to create a three dimensional model of anobject (e.g., a face) within a scene from a viewpoint (e.g., a depthcamera sensor). In some embodiments, in conjunction with imaging module143 (also called a camera module), depth camera sensor 175 is optionallyused to determine a depth map of different portions of an image capturedby the imaging module 143. In some embodiments, a depth camera sensor islocated on the front of device 100 so that the user's image with depthinformation is, optionally, obtained for video conferencing while theuser views the other video conference participants on the touch screendisplay and to capture selfies with depth map data. In some embodiments,the depth camera sensor 175 is located on the back of device, or on theback and the front of the device 100. In some embodiments, the positionof depth camera sensor 175 can be changed by the user (e.g., by rotatingthe lens and the sensor in the device housing) so that a depth camerasensor 175 is used along with the touch screen display for both videoconferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 is, optionally, coupled to inputcontroller 160 in I/O subsystem 106. Proximity sensor 166 optionallyperforms as described in U.S. patent application Ser. No. 11/241,839,“Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “ProximityDetector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient LightSensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862,“Automated Response To And Sensing Of User Activity In PortableDevices”; and Ser. No. 11/638,251, “Methods And Systems For AutomaticConfiguration Of Peripherals,” which are hereby incorporated byreference in their entirety. In some embodiments, the proximity sensorturns off and disables touch screen 112 when the multifunction device isplaced near the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled to an inputcontroller 160 in I/O subsystem 106. Accelerometer 168 optionallyperforms as described in U.S. Patent Publication No. 20050190059,“Acceleration-based Theft Detection System for Portable ElectronicDevices,” and U.S. Patent Publication No. 20060017692, “Methods AndApparatuses For Operating A Portable Device Based On An Accelerometer,”both of which are incorporated by reference herein in their entirety. Insome embodiments, information is displayed on the touch screen displayin a portrait view or a landscape view based on an analysis of datareceived from the one or more accelerometers. Device 100 optionallyincludes, in addition to accelerometer(s) 168, a magnetometer and a GPS(or GLONASS or other global navigation system) receiver for obtaininginformation concerning the location and orientation (e.g., portrait orlandscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3 )stores device/global internal state 157, as shown in FIGS. 1A and 3 .Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 are, optionally, used to manage an address bookor contact list (e.g., stored in application internal state 192 ofcontacts module 137 in memory 102 or memory 370), including: addingname(s) to the address book; deleting name(s) from the address book;associating telephone number(s), e-mail address(es), physicaladdress(es) or other information with a name; associating an image witha name; categorizing and sorting names; providing telephone numbers ore-mail addresses to initiate and/or facilitate communications bytelephone 138, video conference module 139, e-mail 140, or IM 141; andso forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 are optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in contacts module 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation, anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages optionally include graphics, photos, audio files, videofiles and/or other attachments as are supported in an MMS and/or anEnhanced Messaging Service (EMS). As used herein, “instant messaging”refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150are, optionally, used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154are, optionally, used to receive, display, modify, and store maps anddata associated with maps (e.g., driving directions, data on stores andother points of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs (such as computer programs(e.g., including instructions)), procedures, or modules, and thusvarious subsets of these modules are, optionally, combined or otherwiserearranged in various embodiments. For example, video player module is,optionally, combined with music player module into a single module(e.g., video and music player module 152, FIG. 1A). In some embodiments,memory 102 optionally stores a subset of the modules and data structuresidentified above. Furthermore, memory 102 optionally stores additionalmodules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3 ) includes event sorter 170 (e.g.,in operating system 126) and a respective application 136-1 (e.g., anyof the aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit or a higher level object from which application 136-1 inheritsmethods and other properties. In some embodiments, a respective eventhandler 190 includes one or more of: data updater 176, object updater177, GUI updater 178, and/or event data 179 received from event sorter170. Event handler 190 optionally utilizes or calls data updater 176,object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (e.g., 187-1 and/or 187-2) include, for example, touch begin,touch end, touch movement, touch cancellation, and multiple touching. Inone example, the definition for event 1 (187-1) is a double tap on adisplayed object. The double tap, for example, comprises a first touch(touch begin) on the displayed object for a predetermined phase, a firstliftoff (touch end) for a predetermined phase, a second touch (touchbegin) on the displayed object for a predetermined phase, and a secondliftoff (touch end) for a predetermined phase. In another example, thedefinition for event 2 (187-2) is a dragging on a displayed object. Thedragging, for example, comprises a touch (or contact) on the displayedobject for a predetermined phase, a movement of the touch acrosstouch-sensitive display 112, and liftoff of the touch (touch end). Insome embodiments, the event also includes information for one or moreassociated event handlers 190.

In some embodiments, event definitions 186 include a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 optionally also include one or more physical buttons, such as“home” or menu button 204. As described previously, menu button 204 is,optionally, used to navigate to any application 136 in a set ofapplications that are, optionally, executed on device 100.Alternatively, in some embodiments, the menu button is implemented as asoft key in a GUI displayed on touch screen 112.

In some embodiments, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 is, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orcomputer programs (e.g., sets of instructions or including instructions)need not be implemented as separate software programs (such as computerprograms (e.g., including instructions)), procedures, or modules, andthus various subsets of these modules are, optionally, combined orotherwise rearranged in various embodiments. In some embodiments, memory370 optionally stores a subset of the modules and data structuresidentified above. Furthermore, memory 370 optionally stores additionalmodules and data structures not described above.

Attention is now directed towards embodiments of user interfaces thatare, optionally, implemented on, for example, portable multifunctiondevice 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 is labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3 ) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3 ) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 359) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 357 for generating tactile outputsfor a user of device 300.

Although some of the examples that follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface)optionally includes one or more intensity sensors for detectingintensity of contacts (e.g., touches) being applied. The one or moreintensity sensors of touch screen 504 (or the touch-sensitive surface)can provide output data that represents the intensity of touches. Theuser interface of device 500 can respond to touches based on theirintensity, meaning that touches of different intensities can invokedifferent user interface operations on device 500.

Exemplary techniques for detecting and processing touch intensity arefound, for example, in related applications: International PatentApplication Serial No. PCT/US2013/040061, titled “Device, Method, andGraphical User Interface for Displaying User Interface ObjectsCorresponding to an Application,” filed May 8, 2013, published as WIPOPublication No. WO/2013/169849, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, published as WIPO Publication No.WO/2014/105276, each of which is hereby incorporated by reference intheir entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, intensity sensor 524 (e.g., contact intensity sensor). Inaddition, I/O section 514 can be connected with communication unit 530for receiving application and operating system data, using Wi-Fi,Bluetooth, near field communication (NFC), cellular, and/or otherwireless communication techniques. Device 500 can include inputmechanisms 506 and/or 508. Input mechanism 506 is, optionally, arotatable input device or a depressible and rotatable input device, forexample. Input mechanism 508 is, optionally, a button, in some examples.

Input mechanism 508 is, optionally, a microphone, in some examples.Personal electronic device 500 optionally includes various sensors, suchas GPS sensor 532, accelerometer 534, directional sensor 540 (e.g.,compass), gyroscope 536, motion sensor 538, and/or a combinationthereof, all of which can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can include one or morenon-transitory computer-readable storage mediums, for storingcomputer-executable instructions, which, when executed by one or morecomputer processors 516, for example, can cause the computer processorsto perform the techniques described below, including processes 700 and900 (FIGS. 7 and 9 ). A computer-readable storage medium can be anymedium that can tangibly contain or store computer-executableinstructions for use by or in connection with the instruction executionsystem, apparatus, or device. In some examples, the storage medium is atransitory computer-readable storage medium. In some examples, thestorage medium is a non-transitory computer-readable storage medium. Thenon-transitory computer-readable storage medium can include, but is notlimited to, magnetic, optical, and/or semiconductor storages. Examplesof such storage include magnetic disks, optical discs based on CD, DVD,or Blu-ray technologies, as well as persistent solid-state memory suchas flash, solid-state drives, and the like. Personal electronic device500 is not limited to the components and configuration of FIG. 5B, butcan include other or additional components in multiple configurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that is, optionally, displayed on thedisplay screen of devices 100, 300, and/or 500 (FIGS. 1A, 3, and 5A-5B).For example, an image (e.g., icon), a button, and text (e.g., hyperlink)each optionally constitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider, or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionally,based on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholdsoptionally includes a first intensity threshold and a second intensitythreshold. In this example, a contact with a characteristic intensitythat does not exceed the first threshold results in a first operation, acontact with a characteristic intensity that exceeds the first intensitythreshold and does not exceed the second intensity threshold results ina second operation, and a contact with a characteristic intensity thatexceeds the second threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more thresholds is used to determine whether or not to perform one ormore operations (e.g., whether to perform a respective operation orforgo performing the respective operation), rather than being used todetermine whether to perform a first operation or a second operation.

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that are implemented on an electronic device,such as portable multifunction device 100, device 300, or device 500.

FIGS. 6A-6V illustrate exemplary user interfaces for configuring and/orusing a lock accessory, in accordance with some embodiments. The userinterfaces in these figures are used to illustrate the processesdescribed below, including the processes in FIG. 7 .

FIG. 6A illustrates electronic device 600 displaying, on display 602,first user interface 604 corresponding to a home automation system. AtFIG. 6A, first user interface 604 includes home user interface object604 a, add user interface object 604 b, status indicator region 606,favorite scenes region 608, and favorite accessory region 610.

As set forth below with reference to FIG. 8A, home user interface object604 a corresponds to one or more settings of the home automation systemand/or access to particular accessory devices of the home automationsystem. Status indicator region 606 includes first status indicator 606a and second status indicator 606 b each corresponding to an accessorydevice and/or a group of accessory devices that are determined to be ina predefined mode (e.g., an on mode, an unlocked mode, an open mode, anerror mode, and/or an active mode). Thus, status indicator region 606provides an indication of a status of one or more accessory devices ofthe home automation system that a user is likely to want to quicklycontrol (e.g., cause electronic device 600 to adjust a mode and/orsetting of the one or more accessory devices when activated).

Favorite scenes region 608 includes several objects for activatingscenes, including first scene user interface object 608 a for activatinga ‘ready for bed’ scene and second scene user interface object 608 b foractivating an ‘good night’ scene. When a scene is activated, electronicdevice 600 causes respective accessory devices corresponding to eachscene to change modes to respective modes for the activated scene. Forexample, activation of first scene user interface object 608 a causesmusic to stop playing on a smart speaker and the entryway lightaccessory to turn off (or stay off).

Favorite accessory region 610 includes several accessory user interfaceobjects 610 a-610 g for causing an adjustment to a mode for respectiveaccessory devices associated with each object. For example, in responseto detecting user input corresponding to first accessory user interfaceobject 610 a, electronic device 600 causes a dining room light to adjustfrom an on mode to an off mode and/or causes electronic device 600 todisplay a dining room light user interface enabling additional controlsof the dining room light (e.g., the dining room light user interfaceenables electronic device 600 to adjust a brightness setting and/or acolor temperature setting of dining room light).

At FIG. 6A, electronic device 600 detects user input 650 a (e.g., a tapgesture) corresponding to selection of add user interface object 604 b.In response to detecting user input 650 a, electronic device 600displays options user interface 612 including add accessory option 612 aand add scene option 612 b. In some embodiments, in response todetecting user input corresponding to add scene option 612 b, electronicdevice 600 displays an add scene user interface that enables a user toselect one or more accessories and/or particular modes for the one ormore accessories associated with a new scene. In some embodiments, inresponse to creating the new scene, electronic device 600 displays acorresponding additional scene user interface object in favorite scenesregion 608 of first user interface 604.

At FIG. 6A, electronic device 600 detects user input 650 b (e.g., a tapgesture) corresponding to add accessory option 612 a of options userinterface 612. In response to detecting user input 650 b, electronicdevice 600 displays add accessory user interface 614, as shown at FIG.6B.

At FIG. 6B, add accessory user interface 614 includes camera field ofview 614 a, first details region 614 b, second details region 614 c, andmanual setup user interface object 614 d.

First details region 614 b of add accessory user interface 614 includesa visual indication of instructions for a first option for adding anaccessory device (e.g., a new accessory device) to the home automationsystem. For instance, first details region 614 b includes the visualindication, which prompts a user to position a portion of packaging ofthe accessory device that includes a code (e.g., a QR code, a bar code,an alphanumeric code) within a field of view of the camera of electronicdevice 600. Camera field of view 614 a is a visual representation of afield of view of a camera of electronic device 600. At FIG. 6B, camerafield of view 614 a includes a visual representation of a portion of thepackaging of a lock accessory having code 616 that is within the fieldof view of the camera of electronic device 600. When code 616 is withinthe field of view of the camera (e.g., and while displaying addaccessory user interface 614), electronic device 600 detects code 616.In response to detecting code 616, electronic device 600 displays firstaccessory user interface 618, as shown in FIG. 6C. For example, the lockaccessory is an electronic lock (e.g., a smart lock) that can be (or is)installed in a door (e.g., of a home) to control whether the door islocked or unlocked (and therefore can be opened) (e.g., via a deadboltand/or latch).

At FIG. 6B, second details region 614 c of add accessory user interface614 includes a visual indication of instructions for a second option foradding an accessory device (e.g., a new accessory device) to the homeautomation system. For instance, second details region 614 c includesthe visual indication, which prompts a user to position the accessorydevice proximate to (e.g., within a predefined distance of) electronicdevice 600. In some embodiments, in response to detecting that theaccessory device is within a predefined distance of electronic device600, electronic device 600 detects the accessory device and displaysfirst accessory user interface 618, as shown in FIG. 6C.

At FIG. 6B, manual setup user interface object 614 d corresponds to amanual setup process for adding an accessory device (e.g., a newaccessory device) to the home automation system. In some embodiments, inresponse to detecting user input corresponding to manual setup userinterface object 614 d, electronic device 600 displays a detection userinterface that prompts a user to position electronic device 600proximate to the accessory device and/or to turn the accessory deviceon.

At FIG. 6C, first accessory user interface 618 includes visualrepresentation 618 a of the accessory device that has been detected byelectronic device 600 (e.g., via code 616 and/or via a proximity to theaccessory device), identifier 618 b of the accessory device that hasbeen detected by electronic device 600, and add user interface object618 c. Visual representation 618 a includes an image of a type ofaccessory device detected by electronic device 600. For example, at FIG.6C, visual representation 618 a includes an image of lock accessory 620having keypad 620 a. In some embodiments, visual representation 618 acorresponds to a type of accessory that electronic device 600 detectsvia code 616 and/or via establishing a wireless communication with theaccessory device. In some embodiments, visual representation 618 aincludes features that are particular to the accessory device, such askeypad 620 a. In some embodiments, visual representation 618 a includesa generic image corresponding to a type of accessory device detected byelectronic device 600 without including specific features of theaccessory device detected by electronic device 600. At FIG. 6C,identifier 618 b (e.g., ‘Lock’) includes a description of the accessorydevice and/or a type of accessory device.

At FIG. 6C, electronic device 600 detects user input 650 c (e.g., a tapgesture) corresponding to selection of add user interface object 618 c.In response to detecting user input 650 c, electronic device 600displays location user interface 622, as shown at FIG. 6D.

At FIG. 6D, location user interface 622 enables electronic device 600 toassociate the accessory device with a location of the home associatedwith the home automation system. At FIG. 6D, location user interface 622includes first location indicator 622 a (e.g., ‘Front Door’), secondlocation indicator 622 b (e.g., ‘Garage’), third location indicator 622c (e.g., ‘Side Door’), and fourth location indicator 622 d (e.g., ‘BackDoor’). Electronic device 600 displays focus indicator 622 e (e.g., abox and/or border) around first location indicator 622 a. As such, inresponse to detecting user input corresponding to continue userinterface object 622 f, electronic device 600 associates the accessorydevice with the location of the home corresponding to first locationindicator 622 a (e.g., the ‘Front Door’ location). In some embodiments,electronic device 600 is configured to display focus indicator 622 earound one of location indicators 622 b-622 d instead of around locationindicator 622 a. For instance, in response to detecting user input(e.g., a swipe gesture) on location user interface 622, electronicdevice 600 displays focus indicator 622 e around second locationindicator 622 b, third location indicator 622 c, or fourth locationindicator 622 d (e.g., based on a magnitude of the user input, such as adistance associated with movement of the swipe gesture). In someembodiments, location user interface 622 includes an add location userinterface object that, when selected via user input and/or when addlocation user interface object includes focus indicator 622 e, enables auser to add a new location for the home (e.g., via an add location userinterface displayed by electronic device 600).

In some embodiments, location indicators 622 a-622 d correspond tolocations of the home associated with the home automation system thathave been created via user input (e.g., electronic device 600 detectsone or more user inputs that cause electronic device 600 to include alocation of the home that can be associated with one or more accessorydevices that are added to the home automation system). In someembodiments, location indicators 622 a-622 d are generated by electronicdevice 600 as suggested locations for which to associate the accessorydevice (e.g., default locations that are associated with the home whenthe home automation system is created by electronic device 600 and/oranother electronic device).

At FIG. 6D, electronic device 600 detects user input 650 d (e.g., a tapgesture) corresponding to selection of continue user interface object622 f (e.g., continue user interface affordance 622 f). In response todetecting user input 650 d, electronic device 600 associates theaccessory device with the front door location of the home and displaysidentification user interface 624, as shown at FIG. 6E.

At FIG. 6E, identification user interface 624 enables a user to input acustom name for the accessory device detected by electronic device 600.Identification user interface 624 includes name user interface object624 a and continue user interface object 624 b. In some embodiments, inresponse to detecting user input corresponding to name user interfaceobject 624 a, electronic device 600 displays a keyboard (e.g., a virtualkeyboard) that enables a user to type alphanumeric characterscorresponding to a name for the accessory device. At FIG. 6E, electronicdevice 600 displays name 624 c (e.g., ‘Front Door Lock’) in name userinterface object 624 a.

In some embodiments, electronic device 600 displays name 624 c inresponse to detecting one or more user inputs on the keyboard afterdetecting user input corresponding to name user interface object 624 a.In some such embodiments, electronic device 600 displays name userinterface object 624 a without name 624 c and displays name 624 c inresponse to detecting one or more user inputs on the keyboard. In someembodiments, electronic device 600 displays name 624 c as a suggestedidentifier for the accessory device based on the location associatedwith the accessory device (e.g., ‘Front Door’ selected via location userinterface 622) and/or based on a type of accessory device detected byelectronic device 600 (e.g., a lock).

At FIG. 6E, electronic device 600 detects user input 650 e (e.g., a tapgesture) corresponding to selection of continue user interface object624 b. In response to detecting user input 650 e, electronic device 600displays accounts user interface 626, as shown at FIG. 6F.

At FIG. 6F, accounts user interface 626 enables a user to add anelectronic key associated with the lock accessory to electronic device600. As set forth below, in some embodiments, adding the electronic keyassociated with the lock accessory to electronic device 600 enables auser to quickly and easily provide authorization and cause electronicdevice 600 to lock and/or unlock the lock accessory. At FIG. 6F,electronic device 600 detects user input 650 f (e.g., a tap gesture)corresponding to selection of continue user interface object 626 a ofaccounts user interface 626. In response to detecting user input 650 f,electronic device 600 adds an electronic key associated with the lockaccessory to electronic device 600. In some embodiments, electronicdevice 600 forgoes displaying accounts user interface 626 and adds anelectronic key associated with the lock accessory to electronic device600 without detecting user input 650 f (e.g., electronic device 600automatically adds the electronic key associated with the lock accessoryto electronic device 600).

In some embodiments, the lock accessory detected by electronic device600 (e.g., via code 616 and/or via establishing a wireless communicationwith the lock accessory) includes a wireless communication feature thatenables electronic device 600 to cause the lock accessory to transitionbetween modes (e.g., a locked mode and an unlocked mode) via wirelesscommunication (e.g., near-field communication, Bluetooth, Wi-Fi, UWB,and/or Zigbee). When electronic device 600 detects that the lockaccessory includes the wireless communication feature and/or in responseto detecting user input 650 f, electronic device 600 displays expressmode user interface 628, as shown at FIG. 6G. When electronic device 600detects that the lock accessory does not include the wirelesscommunication feature, electronic device 600 forgoes displaying expressmode user interface 628 and instead displays the next user interface ofthe configuration process for the lock accessory (e.g., pin userinterface 630, as shown at FIG. 6H).

At FIG. 6G, express mode user interface 628 enables electronic device600 to activate an express mode for the lock accessory. When the expressmode is activated, electronic device 600 causes the lock accessory totransition between modes (e.g., from the unlocked mode to the lockedmode and/or from the locked mode to the unlocked mode) in response todetecting that the lock accessory is within a predefined distance fromelectronic device 600, such as within wireless range, within one foot,within six inches, within three inches, within two inches, within oneinch, and/or within less than one inch from electronic device 600. Insome embodiments, when the express mode is activated, electronic device600 causes the lock accessory to transition between modes withoutrequiring a user to provide (e.g., between the time the lock accessoryis detected within the predefined distance and when an instruction issent to unlock the lock) further authentication, such as a passwordand/or a biometric feature (e.g., facial features and/or a fingerprint),and/or without transitioning electronic device 600 from a lockedmode/state to an unlocked mode/state and independent of thelocked/unlocked mode/state of electronic device 600.

At FIG. 6G, express mode user interface 628 includes activate userinterface object 628 a and skip user interface object 628 b (e.g., skipactivation user interface object 628 b). In response to detecting userinput corresponding to selection of skip user interface object 628 b,electronic device 600 does not activate the express mode. When theexpress mode is not activated, electronic device 600 prompts a user forauthorization before causing the lock accessory to transition betweenmodes (e.g., when the lock accessory is within the predefined distanceof electronic device 600). At FIG. 6G, electronic device 600 detectsuser input 650 g (e.g., a tap gesture) corresponding to selection ofactivate user interface object 628 a. In response to detecting userinput 650 g, electronic device 600 enables the express mode, therebyenabling electronic device 600 to cause the lock accessory to transitionbetween modes when electronic device 600 detects that the lock accessoryis within the predefined distance from electronic device 600 and withoutprompting a user to provide further authentication.

In some embodiments, the lock accessory detected by electronic device600 (e.g., via code 616 and/or via establishing a wireless communicationwith the lock accessory) includes a keypad (e.g., in addition to thewireless communication feature and/or instead of the wirelesscommunication feature). For example, the lock accessory includes anintegrated keypad, and the lock (with integrated keypad) is installed(or to be installed) in a door (e.g., of a home). In some suchembodiments, electronic device 600 is used to set and/or store apersonal identification number (e.g., a “pin”) that can be entered intothe keypad of the lock accessory to cause the lock accessory totransition between modes (e.g., a locked mode and an unlocked mode).When electronic device 600 detects that the lock accessory includes thekeypad and/or in response to detecting user input 650 g, electronicdevice 600 displays pin user interface 630, as shown at FIG. 6H. Whenelectronic device 600 detects that the lock accessory does not include akeypad, electronic device 600 forgoes displaying pin user interface 630and instead displays the next user interface of the configurationprocess for the lock accessory (e.g., confirmation user interface 634shown at FIG. 6J).

At FIG. 6H, pin user interface 630 includes pin indicator 630 a,continue user interface object 630 b, and change pin user interfaceobject 630 c. In some embodiments, when electronic device 600 detectsthat the lock accessory includes the keypad, electronic device 600generates a pin (e.g., a random set of alphanumeric characters) andcommunicates with the lock accessory (e.g., via wireless communication,such as Wi-Fi) so that the pin can be entered into the keypad of thelock accessory to cause the lock accessory to transition between modes.In some such embodiments, electronic device 600 displays the generatedpin via pin indicator 630 a (e.g., ‘4567’). In some embodiments,electronic device 600 suggests an existing pin in pin indicator 630 afor use with the lock accessory, where the existing pin is associatedwith a different lock accessory of the home automation system (e.g.,electronic device 600 suggests that a user set a pin for the lockaccessory that is the same as a pin associated with another lockaccessory of the home automation system). In some embodiments, anaccount of the home automation system is associated with the pin, andthe pin (the same pin) is used to unlock various lock accessories of thehome automation system. A second account of the home automation systemis associated with a second (different) pin, and the second pin is used(e.g., by the user of the second account) to unlock the various lockaccessories of the home automation system.

At FIG. 6H, electronic device 600 detects user input 650 h (e.g., a tapgesture) corresponding to selection of change pin user interface object630 c. In response to detecting user input 650 h, electronic device 600displays change pin user interface 632, as shown at FIG. 6I.Alternatively, electronic device 600 detects user input 650 i (e.g., atap gesture) corresponding to continue user interface object 630 b. Inresponse to detecting user input 650 i, electronic device 600 sets thepin (e.g., ‘4567’) (e.g., corresponding to a particular user) for usewith the lock accessory (e.g., via wireless communication with the lockaccessory) and displays confirmation user interface 634 (e.g., andforgoes displaying change pin user interface 632), as shown at FIG. 6J.

At FIG. 6I, change pin user interface 632 includes pin indicator 632 a,keyboard 632 b, and done user interface object 632 c. At FIG. 6I,computer system 600 has detected one or more user inputs correspondingto keyboard 632 b and displays pin 632 d (e.g., ‘3454’) in pin indicator632 a. As such, change pin user interface 632 allows a user to input apin that electronic device 600 enables for use with the lock accessory(e.g., electronic device 600 communicates with the lock accessory over awireless communication to cause the lock accessory to accept the pin asauthorization for transitioning the lock accessory between modes). AtFIG. 6I, electronic device 600 detects user input 650 j (e.g., a tapgesture) corresponding to selection of done user interface object 632 c.In response to detecting user input 650 j, electronic device 600 setspin 632 d for use with the lock accessory and displays confirmation userinterface 634, as shown at FIG. 6J.

At FIG. 6J, confirmation user interface 634 includes visualrepresentation 634 a of the lock accessory, confirmation indicator 634b, and continue user interface object 634 c. As set forth above withreference to FIG. 6C, visual representation 634 a of the lock accessoryincludes an image of the lock accessory (e.g., a generic image and/or animage with features specific to the lock accessory, such as keypad 634d). Confirmation indicator 634 b includes a visual representationindicating that electronic device 600 successfully added the lockaccessory to the home automation system. At FIG. 6J, electronic device600 detects user input 650 k (e.g., a tap gesture) corresponding tocontinue user interface object 634 c. In response to detecting userinput 650 k, electronic device 600 displays automation user interface636, as shown at FIG. 6K.

At FIG. 6K, automation user interface 636 includes first automation userinterface object 636 a corresponding to a first automation setting forthe lock accessory, second automation user interface object 636 bcorresponding to a second automation setting for the lock accessory, andthird automation user interface object 636 d corresponding to a thirdautomation setting for the lock accessory. For example, at FIG. 6K,first automation user interface object 636 a corresponds to anautomation setting for the lock accessory that, when activated, enableselectronic device 600 to cause the lock accessory to transition from anunlocked mode to an unlocked mode in response to determining thatelectronic device 600 is outside of a predefined distance from the home(e.g., electronic device 600 is disconnected from a Wi-Fi networkassociated with the home automation system and/or electronic device 600is outside of the predefined distance (e.g., based on GPS or otherlocating techniques) from one or more accessories of the home automationsystem).

At FIG. 6K, second automation user interface object 636 b corresponds toan automation setting for the lock accessory that, when activated,enables electronic device 600 to cause the lock accessory to transitionfrom the locked mode to the unlocked mode when electronic device 600 iswithin the predefined distance of the home (e.g., electronic device 600connects to a Wi-Fi network associated with the home automation systemand/or electronic device is within the predefined distance from one ormore accessories of the home automation system). Third automation userinterface object 636 c corresponds to an automation setting for the lockaccessory that, when activated, enables electronic device 600 to causethe lock accessory to transition from the unlocked mode to the lockedmode when electronic device 600 and additional electronic devicesassociated with the home automation system (e.g., smart phones (and/orprimary devices) of other users of the home automation system) areoutside of the predefined distance from the home (e.g., electronicdevice 600 and additional electronic devices associated with the homeautomation system are disconnected from a Wi-Fi network associated withthe home automation system and/or electronic device 600 and alladditional electronic devices associated with the home automation systemare outside of the predefined distance from one or more accessories ofthe home automation system).

At FIG. 6K, each of automation user interface objects 636 a-636 c are inan on state (e.g., the automation settings associated with automationuser interface objects 636 a-636 c are enabled). In some embodiments,electronic device 600 displays automation user interface 636 withautomation user interface objects 636 a-636 c in the on state (e.g.,enabled) in response to detecting user input 650 k. In some embodiments,electronic device 600 displays automation user interface 636 withautomation user interface objects 636 a-636 c in the off state (e.g.,disabled) in response to detecting user input 650 k. In someembodiments, electronic device 600 displays automation user interface636 with one or more of automation user interface objects 636 a-636 c inthe on state (e.g., enabled).

At FIG. 6K, electronic device 600 detects user input 650 l (e.g., a tapgesture) corresponding to selection of third automation user interfaceobject 636 c. In response to detecting user input 650 l, electronicdevice 600 displays third automation user interface object 636 c in theoff state indicating that the third automation setting of the lockaccessory is disabled and/or not activated.

At FIG. 6K, electronic device 600 detects user input 650 m (e.g., a tapgesture) corresponding to selection of done user interface object 636 d.In response to detecting user input 650 k, electronic device 600displays guest user interface 638, as shown at FIG. 6L.

At FIG. 6L, electronic device 600 determines that the home automationsystem includes one or more guests that have been authorized to useand/or access one or more accessories of the home automation system. Forinstance, a user of electronic device 600 and/or another user of anexternal device associated with the home automation system can provide anon-resident of the home access to an existing lock accessory (e.g., alock accessory that is included in and/or has been previously added tothe home automation system and that is different from the lock accessorydetected by electronic device 600 as set forth above with reference toFIGS. 6B-6C), such that the guest can cause the existing lock accessoryto transition between modes (e.g., via an electronic device and/or viainput on a keypad of the lock accessory). When electronic device 600determines that the home automation system includes guests that areauthorized to use and/or access an existing lock accessory (and,optionally, other types of accessories of the home automation system),electronic device 600 displays guest user interface 638. Guest userinterface 638 enables a user of electronic device 600 to authorize oneor more existing guests to use the lock accessory. In contrast, whenelectronic device 600 determines that the home automation system doesnot include guests and/or does not include guests that are authorized touse and/or access an existing lock accessory (and, optionally, othertypes of accessories of the home automation system), electronic device600 forgoes displaying guest user interface 638.

At FIG. 6L, guest user interface 638 includes first guest user interfaceobject 638 a corresponding to a first existing guest of the homeautomation system, second guest user interface object 638 bcorresponding to a second existing guest of the home automation system,continue user interface object 638 c, and skip user interface object 638d.

In response to detecting user input 650 m, electronic device 600displays guest user interface 638 indicating that the guests associatedwith guest user interface objects 638 a-638 b are not authorized toaccess the lock accessory (e.g., guest user interface objects 638 a-638b are displayed without authorization indicator 638 e). In other words,electronic device 600 defaults to not providing authorization to theguests associated with guest user interface objects 638 a-638 b whenelectronic device 600 initially displays guest user interface 638.Instead, electronic device 600 authorizes one or more of the guestsassociated with guest user interface objects 638 a-638 b in response touser input corresponding to selection of one or both guest userinterface objects 638 a-638 b.

At FIG. 6L, electronic device 600 detects user input 650 n (e.g., a tapgesture) corresponding to selection of first guest user interface object638 a. In response to detecting user input 650 n, electronic device 600displays authorization indicator 638 e on first guest user interface 638a (e.g., within first guest user interface object 638 a and/or adjacentto first guest user interface object 638 a). Authorization indicator 638e indicates that electronic device will authorize the first existingguest (e.g., ‘Contractor’) associated with first guest user interfaceobject 638 a to access the lock accessory in response to detecting userinput corresponding to continue user interface object 638 c. In someembodiments, electronic device 600 displays authorization indicator 638e for the second guest (e.g., ‘Delivery Person’) associated with secondguest user interface object 638 b in response to detecting user inputselecting second guest user interface object 638 b.

In some embodiments, before detecting user input 650 n and in responseto detecting user input selecting skip user interface object 638 d,electronic device 600 forgoes authorizing both the first guestassociated with first guest user interface object 638 a and the secondguest associated with second guest user interface object 638 b anddisplays first user interface 604, as shown at FIG. 6M. In someembodiments, a user of electronic device 600 can provide authorizationto the first guest and/or the second guest at a later time (e.g., a timeafter electronic device 600 displays guest user interface 638) via asettings user interface of electronic device 600.

At FIG. 6L, electronic device 600 detects user input 650 o (e.g., a tapgesture) corresponding to selection of continue user interface object638 c. In response to detecting user input 650 o, electronic device 600authorizes the first guest associated with first guest user interfaceobject 638 a to access the lock accessory (e.g., via an external deviceassociated with the first guest and/or via a pin). After detecting userinput 650 o, electronic device 600 displays first user interface 604, asshown at FIG. 6M.

At FIG. 6M, first user interface 604 includes lock accessory userinterface object 640 in favorite accessory region 610. Lock accessoryuser interface object 640 corresponds to the lock accessory thatelectronic device 600 detected and configured as described above withreference to FIGS. 6B-6L. At FIG. 6M, lock accessory user interfaceobject 640 includes identifier 640 a (e.g., ‘Front Door Lock’) andstatus indicator 640 b (e.g., ‘Unlocked’). Lock accessory user interfaceobject 640 thus includes visual indications providing information (e.g.,a current mode, such as ‘Unlocked’) related to the lock accessorycorresponding to lock accessory user interface object 640.

In some embodiments, electronic device 600 displays lock accessory userinterface object 640 in favorite accessory region 610 in response todetecting one or more user inputs designating the lock accessorycorresponding to lock accessory user interface object 640 as a favoriteaccessory. In some embodiments, electronic device 600 displays lockaccessory user interface object 640 in favorite accessory region 610 inresponse to determining that a setup process for the lock accessory iscompleted (e.g., in response to detecting user input 650 o).

At FIG. 6M, electronic device 600 detects user input 650 p (e.g., a longpress gesture) corresponding to lock accessory user interface object640. In response to detecting user input 650 p, electronic device 600displays front door lock user interface 642, as shown at FIG. 6N.

At FIG. 6N, front door lock user interface 642 includes mode userinterface object 644 and settings user interface object 642 a. Mode userinterface object 644 includes indicator 644 a corresponding to a currentmode of the lock accessory (e.g., an unlocked mode). When mode userinterface object 644 is selected via user input, electronic device 600causes the lock accessory to transition from a first mode (e.g., theunlocked mode) to a second mode (e.g., a locked mode). At FIG. 6N, modeuser interface object 644 is in a first position and indicator 644 aincludes a visual representation of an unlocked lock, thereby indicatingthat the lock accessory is in an unlocked mode. In response to detectinguser input 650 q (e.g., a swipe down gesture and/or a tap gesture) onmode user interface object 644, electronic device 600 displays mode userinterface object 644 in a second position and causes the lock accessoryto transition from the unlocked mode to a locked mode. In someembodiments, in response to detecting user input 650 q, electronicdevice 600 displays indicator 644 a as having a visual representation ofa locked lock to indicate that the lock accessory has transitioned tothe locked mode.

Front door lock user interface 642 enables electronic device 600 tocause the lock accessory to transition between modes (e.g., locked andunlocked). In some embodiments, electronic device 600 is configured tocause the lock accessory to transition between modes in response todetecting user input corresponding to mode user interface object 644when a set of criteria is met. For example, in some embodiments, the setof criteria includes electronic device 600 being connected to the samenetwork (e.g., Wi-Fi network) as the lock accessory, electronic device600 being within a predefined distance of the lock accessory, and/orelectronic device 600 being in direct communication with the lockaccessory (e.g., via a short-range communication connection, such asBluetooth). In some embodiments, when the set of criteria is not met,electronic device 600 is unable to cause the lock accessory totransition between modes in response to detecting user inputcorresponding to mode user interface object 644. In some embodiments,when the set of criteria is not met, electronic device 600 forgoesdisplaying front door lock user interface 642 in response to detectinguser input 650 p.

At FIG. 6N, electronic device 600 detects user input 650 r correspondingto selection of settings user interface object 642 a of front door lockuser interface 642. In response to detecting user input 650 r,electronic device 600 displays first settings user interface 646, asshown at FIG. 6O.

At FIG. 6O, first settings user interface 646 includes identifier 646 acorresponding to a name and/or other identifier of the lock accessory,settings region 646 b, automations region 646 c, manage access userinterface object 646 d, notifications user interface object 646 e, anddetails region 646 f. In some embodiments, electronic device 600 isconfigured to adjust and/or change a location designation of the lockaccessory and/or adjust whether lock accessory user interface object 640is displayed in favorite accessory region 610 in response to one or moreuser inputs corresponding to settings region 646 b. In some embodiments,electronic device 600 is configured to enable, disable, and/or createautomation settings for the lock accessory in response to one or moreuser inputs corresponding to automations region 646 c. In someembodiments, electronic device 600 is configured to displayauthorization statuses, authorize, and/or revoke authorization for oneor more users in response to user input selecting manage access userinterface object 646 d. In some embodiments, electronic device 600 isconfigured to display notification options, enable notifications, and/ordisable notifications for the lock accessory in response to user inputselecting notifications user interface object 646 e.

At FIG. 6O, electronic device 600 detects user input 650 s (e.g., aswipe right gesture) while displaying first settings user interface 646.After detecting user input 650 s, electronic device 600 navigates to anaccounts application (e.g., an electronic wallet application) ofelectronic device 600 and displays accounts user interface 648, as shownat FIG. 6P.

At FIG. 6P, accounts user interface 648 includes first electronic keyuser interface object 648 a and electronic key stack 648 b. Firstelectronic key user interface object 648 a corresponds to an electronickey for one or more lock accessories, including the lock accessory, ofthe home automation system. As set forth above with reference to FIG.6F, electronic device 600 includes first electronic key user interfaceobject 648 a and/or otherwise associates the lock accessory with firstelectronic key user interface object 648 a in response to detecting userinput 650 f during the configuration process of the lock accessory. Insome embodiments, first electronic key user interface object 648 aincludes an appearance, such as a color and/or finish, that matches anappearance of the lock accessory. In some such embodiments, electronicdevice 600 receives data from the lock accessory (e.g., via a wirelesscommunication connection) corresponding to a visual appearance of thelock accessory and displays first electronic key user interface object648 a to resemble and/or simulate an appearance of the lock accessory.

In some embodiments, electronic key stack 648 b corresponds to aplurality of electronic keys, passes, and/or account credentials forwhich electronic device 600 has received authorization (e.g., electroniccar keys, boarding passes, transportation accounts, transactionaccounts, and/or gift cards).

At FIG. 6P, electronic device 600 detects user input 650 t (e.g., a tapgesture) corresponding to selection of key settings user interfaceobject 648 c. In response to detecting user input 650 t, electronicdevice 600 displays key settings user interface 652, as shown at FIG.6Q.

At FIG. 6Q, key settings user interface 652 includes first key userinterface object 648 a, home application user interface object 652 a,pin code region 652 b, notifications user interface object 652 c,express mode region 654, and remove key user interface object 652 d. Insome embodiments, in response to detecting user input corresponding toselection of home application user interface object 652 a, electronicdevice 600 displays first user interface 604 and/or front door lock userinterface 642. In some embodiments, electronic device 600 is configuredto change a pin associated with one or more lock accessories (e.g., andthe lock accessory) of the home automation system in response to userinput selecting pin code region 652 b (e.g., to change the pin for anaccount of the home automation system). In some embodiments, electronicdevice 600 is configured to enable and/or disable notifications for thelock accessory (and, optionally, other lock accessories of the homeautomation system) in response to user input selecting notificationsuser interface object 652 c. In some embodiments, electronic device 600is configured to remove and/or revoke authorization of electronic device600 for the lock accessory (and, optionally, other lock accessories ofthe home automation system) in response to user input corresponding toremove key user interface object 652 d.

As set forth above, express mode enables electronic device 600 to causethe lock accessory to transition between modes when electronic device600 is within a predefined distance of the lock accessory (and when thelock accessory includes a wireless communication feature) withoutrequiring further authentication from a user of electronic device 600.At FIG. 6Q, express mode region 654 includes express mode user interfaceobject 654 a and express mode settings user interface object 654 b. Insome embodiments, electronic device 600 displays an express modesettings user interface in response to detecting user input selectingexpress mode settings user interface object 654 b. In some suchembodiments, the express mode settings user interface enables electronicdevice 600 to adjust settings corresponding to the express mode, such aswhich lock accessories of the home automation system are authorizedand/or selected for use with the express mode.

At FIG. 6Q, express mode user interface object 654 a includes indicator654 c indicating that the express mode for the lock accessory (and,optionally, other lock accessories of the home automation system) iscurrently disabled (e.g., ‘Off’). At FIG. 6Q, electronic device 600detects user input 650 u (e.g., a tap gesture) corresponding toselection of express mode user interface object 654 a. In response todetecting user input 650 u, electronic device 600 prompts a user forauthentication to enable the express mode, as shown at FIG. 6R.

Because the express mode enables a user to cause the lock accessory totransition between modes without requiring further authorization fromthe user, electronic device 600 prompts a user to provide authenticationto enable the express mode (e.g., so that an identity of the user ofelectronic device 600 is confirmed before electronic device 600 isauthorized to use the express mode). At FIG. 6R, electronic device 600displays authentication user interface object 656, which prompts a userto provide a biometric feature, such as one or more facial featuresand/or a fingerprint, as an authentication input for enabling theexpress mode. In some embodiments, authentication user interface object656 prompts the user to provide another authentication input, such as apassword. At FIG. 6R, in response to detecting the biometric feature ofa user (e.g., via a camera and/or a fingerprint sensor of electronicdevice 600), electronic device 600 compares the detected biometricfeature to biometric feature data of an authorized user of electronicdevice (e.g., biometric feature data stored and/or accessible byelectronic device). At FIG. 6R, electronic device 600 determines thatthe detected biometric feature matches the biometric feature data of theauthorized user and enables the express mode for the lock accessory(and, optionally, other lock accessories of the home automation system).At FIG. 6R, after determining that the detected biometric featurematches the biometric feature data, electronic device 600 displaysindicator 654 c (e.g., updates display of indicator 654 c) indicatingthat the express mode has been enabled (e.g., ‘On’).

After electronic device 600 enables the express mode, electronic device600 is configured to cause the lock accessory to transition betweenmodes when electronic device 600 is within the predefined distance ofthe lock accessory (and when the lock accessory includes a wirelesscommunication feature (e.g., a near-field communication receiver and/ortag)). At FIG. 6S, electronic device 600 is positioned proximate to lockaccessory 658 (e.g., the lock accessory detected by electronic device600 and configured by electronic device 600 as described above withreference to FIGS. 6B-6L). At FIG. 6S, electronic device 600 is within apredefined distance of lock accessory 658. In some embodiments, thepredefined distance is within one foot, within six inches, within fiveinches, within two inches, within one inch, and/or within less than oneinch of (e.g., in contact with) lock accessory 658. As described below,when electronic device 600 determines and/or detects that electronicdevice 600 is within the predefined distance of lock accessory 658 andwhen the express mode is enabled (e.g., lock accessory 658 includes awireless communication feature), electronic device 600 causes lockaccessory 658 to transition between modes (e.g., from a locked mode toan unlocked mode or from the unlocked mode to the locked mode).

At FIG. 6S, electronic device 600 displays lock user interface 660indicating that electronic device 600 is locked (e.g., one or morefeatures and/or functions of electronic device 600 are locked and/orblocked). In some embodiments, electronic device 600 unlocks (and/orunblocks the one or more features and/or functions) in response todetecting an authentication user input, such as a passcode, a password,and/or a biometric feature (e.g., one or more facial features and/or afingerprint detected via a biometric sensor (e.g., a camera and/or afingerprint sensor) of electronic device 600). At FIG. 6S, whileelectronic device 600 is locked (and, optionally displays lock userinterface 660) and while the express mode is enabled, electronic device600 detects that lock accessory 658 is within the predefined distance ofelectronic device 600. In response to detecting that lock accessory 658is within the predefined distance of electronic device 600, electronicdevice 600 causes (e.g., sends a wireless communication to) lockaccessory 658 to transition between modes (e.g., to unlock), as shown atFIG. 6T. At FIG. 6S, electronic device causes lock accessory 658 totransition between modes while displaying lock user interface 660 andwithout prompting a user to provide an authentication input. Therefore,when the express mode is enabled, electronic device 600 causes lockaccessory 658 to transition between modes (e.g., to unlock) withoutrequiring a user to provide an authentication input and/or otherwiseunlock electronic device 600.

At FIG. 6T, after electronic device 600 causes lock accessory 658 totransition between modes, electronic device 600 displays mode transitionuser interface 662. Mode transition user interface 662 includes firstelectronic key user interface object 648 a and status indicator 662 a.Displaying first electronic key user interface object 648 a provides anindication to a user of electronic device 600 that electronic device 600used an electronic key associated with first electronic key userinterface object 648 a (and associated with lock accessory 658) to causelock accessory 658 to transition between modes. In some embodiments, auser of electronic device 600 did not intend to cause lock accessory 658to transition between modes, and thus, the user can take further actionto cause lock accessory 658 to return to a preferred mode. Statusindicator 662 a notifies a user of electronic device 600 that electronicdevice 600 received an indication (e.g., from lock accessory 658 and/orfrom an intermediate device in communication with electronic device 600and lock accessory 658) that lock accessory 658 successfully transitionbetween modes.

In some embodiments, electronic device 600 displays mode transition userinterface 662 for a predefined period of time (e.g., 10 seconds, 5seconds, and/or 3 seconds) before ceasing to display mode transitionuser interface 662 and displaying lock user interface 660. In someembodiments, electronic device 600 forgoes displaying mode transitionuser interface 662 after receiving and indication that lock accessory658 transitioned between modes (e.g., electronic device 600 continues todisplay lock user interface 660).

FIGS. 6U and 6V illustrate exemplary user interfaces that includenotifications corresponding to lock accessory 658 (and/or another lockaccessory of the home automation system). At FIG. 6U, electronic device600 displays unlock notification 664 indicating that lock accessory 658(and/or another lock accessory of the home automation system)transitioned from a locked mode to an unlocked mode via a pin enteredinto a keypad of lock accessory 658. The notification may include anindication of which user and/or device associated with a user interactedwith lock accessory 658. In this case, Jane Appleseed (and/or anauthorized device of Jane Appleseed) unlocked the front door lock withthe pin code assigned to Jane Appleseed. At FIG. 6U, electronic device600 displays unlock notification 664 on lock user interface 660. In someembodiments, electronic device 600 displays unlock notification 664while electronic device 600 is in an unlocked state and displayinganother user interface.

In some embodiments, electronic device 600 displays unlock notification664 in response to detecting and/or receiving an indication that lockaccessory 658 transitioned from a locked mode to an unlocked mode via apin entered into a keypad of lock accessory 658. In some embodiments,electronic device 600 displays unlock notification 664 in response todetecting and/or receiving an indication that a pin of a first set ofpins was entered into a keypad of lock accessory 658 and caused lockaccessory 658 to transition from the locked mode to the unlocked mode.In some such embodiments, the first set of pins correspond to users thatare different from the user of electronic device 600 (e.g., pinscorresponding to users associated with different accounts than anaccount of electronic device 600) and/or users that are not designatedas residents of the home (e.g., users that are designated as guests andhave access to lock accessory 658 via a pin). In some embodiments, whenelectronic device 600 detects and/or receives an indication that a pinthat is not included in the first set of pins was entered into a keypadof lock accessory 658 and caused lock accessory 658 to transition fromthe locked mode to the unlocked mode, electronic device 600 forgoesdisplaying unlock notification 664. In some embodiments, electronicdevice 600 displays unlock notification 664 when electronic device 600determines that lock accessory 658 (and/or another lock accessory of thehome automation system) includes a keypad. In some embodiments, whenelectronic device 600 detects and/or receives an indication that a pinthat is not authorized to cause lock accessory 658 to transition betweenmodes was entered at a keypad of lock accessory 658, electronic device600 displays a notification indicating that an unauthorized pin wasattempted to cause lock accessory 658 to transition between modes (e.g.,but lock accessory 658 did not transition between modes).

At FIG. 6V, electronic device 666 displays, via display 666 a, new lockaccessory notification 668 indicating that lock accessory 658 (and/oranother lock accessory of the home automation system) has been newlyadded to the home automation system. At FIG. 6V, electronic device 666displays new lock accessory notification 668 on lock user interface 670.In some embodiments, electronic device 666 displays new lock accessorynotification 668 while electronic device 666 is in an unlocked state anddisplaying another user interface.

In some embodiments, electronic device 666 is different from electronicdevice 600. For instance, in some embodiments, electronic device 666corresponds to a user that has been granted authorization for the homeautomation system, but the user associated with electronic device 666did not configure lock accessory 658 (e.g., as described above withreference to FIGS. 6A-6L). Accordingly, users that have been grantedauthorization for the home automation system receive new lock accessorynotification 668 when lock accessory 658 is added to the home automationsystem so that users can configure and/or customize various settings forlock accessory 658 via electronic device 666 (e.g., express modesettings, notification settings, pin settings, and/or automationsettings). In some embodiments, electronic devices associated with usersthat are designated as guests of the home automation system do notgenerate and/or display new lock accessory notification 668.

At FIG. 6V, electronic device 666 detects user input 650 v (e.g., a tapgesture) corresponding to selection of new lock accessory notification668. In some embodiments, in response to detecting user input 650 v,electronic device 666 displays accounts user interface 626 (e.g., asshown at FIG. 6F), express mode user interface 628 (e.g., as shown atFIG. 6G), and/or pin user interface 630 (e.g., as shown at FIG. 6H) sothat the user of electronic device 666 can adjust one or more settingsfor lock accessory 658 via electronic device 666.

FIG. 7 is a flow diagram illustrating a method for configuring a lockaccessory using a computer system in accordance with some embodiments.Method 700 is performed at a computer system (e.g., 100, 300, 500, or600) (e.g., a smartphone, a tablet, and/or a smartwatch) that is incommunication with (e.g., wirelessly or by wire, and/or integrates orincludes) a display generation component (e.g., a display ortouch-sensitive display) and one or more input devices (e.g., atouch-sensitive surface and/or a keyboard). Some operations in method700 are, optionally, combined, the orders of some operations are,optionally, changed, and some operations are, optionally, omitted.

As described below, method 700 provides an intuitive way for configuringa lock accessory. The method reduces the cognitive burden on a user forconfiguring a lock accessory, thereby creating a more efficienthuman-machine interface. For battery-operated computing devices,enabling a user to configure a lock accessory faster and moreefficiently conserves power and increases the time between batterycharges.

The computer system (e.g., 600) receives (702), via the one or moreinput devices, a request (e.g., 650 c) to configure an electronic lock(e.g., 658) (e.g., a door lock, such as for controlling access to ahome/building doorway) that is separate from (e.g., that is notphysically integrated into the computer system; that does not power on(or off) when the computer system is powered on (or off)) the computersystem (e.g., 600). In some embodiments, the computer system is incommunication (e.g., wireless communication) with the electronic lock.

In response to receiving the request (e.g., 650 c) to configure theelectronic lock (e.g., 658), the computer system (e.g., 600) starts(704) a configuration process for configuring the electronic lock.

During the configuration process (706) for configuring the electroniclock, in accordance with a determination that the electronic lockincludes a short-range communication feature for communicating viashort-range wireless communication (e.g., includes a near fieldcommunication (NFC) reader, includes WiFi communication capabilities,and/or includes ultra-wideband (UWB) communication capabilities) (andoptionally in response to receiving a first configuration user inputreceived during the configuration process), the computer system (e.g.,600) displays (708), via the display generation component, an option(e.g., 628 and/or 628 a) (e.g., a graphical user interface object) toconfigure a first account (e.g., corresponding to a first digital key ofan electronic wallet for unlocking the lock) of the computer system toprovide credentials (e.g., to unlock the electronic lock) viashort-range communication (e.g., via NFC, WiFi, and/or UWB) withoutrequiring authentication (e.g., without requiring the user to enter apassword/passcode at the computer system, without requiringauthentication via fingerprint and/or facial recognition when theelectronic lock requests a credential from the computer system; and/orwithout requiring separate authentication (e.g., separate authenticationbeyond any authentication provided to unlock the computer system; afterthe computer system has been authenticated and while the computer systemis in an unlocked state) specifically for providing credentials to theelectronic lock).

During the configuration process (706) for configuring the electroniclock, in accordance with a determination that the electronic lock doesnot include the short-range communication feature (e.g., does notinclude NFC reader, does not include WiFi communication capabilities,and/or does not include a UWB communication capabilities) (andoptionally in response to receiving the first configuration user inputreceived during the configuration process), the computer system (e.g.,600) forgoes displaying (710), via the display generation component, ofthe option to configure the first account of the computer system toprovide credentials without requiring authentication.

During the configuration process (706) for configuring the electroniclock, in accordance with a determination that the electronic lockincludes a keypad feature (e.g., includes a numeric and/or alphanumerickeypad and/or is configurable to display a numeric and/or alphanumerickeypad) (and optionally in response to receiving a second configurationuser input received during the configuration process), the computersystem (e.g., 600) displays (712), via the display generation component,an option (e.g., 630, 630 c) to configure a code (e.g., a numericalcode, an alphabetical code, an alphanumerical code) of the first accountof the computer system to be used for unlocking the electronic lock viathe keypad feature of the electronic lock.

During the configuration process (706) for configuring the electroniclock, in accordance with a determination that the electronic lock doesnot include the keypad feature (e.g., does not include a numeric and/oralphanumeric keypad and/or is not configurable to display a numericand/or alphanumeric keypad) (and optionally in response to receiving thesecond configuration user input received during the configurationprocess), the computer system (e.g., 600) forgoes displaying (714), viathe display generation component, of the option to configure a code(e.g., a numerical code, an alphabetical code, an alphanumerical code)of the first account of the computer system to be used for unlocking theelectronic lock.

In some embodiments, the electronic lock is a smart lock. In someembodiments, the electronic lock includes a bolt and/or cylinderconnected to a motor using an actuator. In some embodiments, theelectronic lock is configured to perform locking and unlockingoperations (e.g., via activation of the actuator), such as on a door,based on receiving authorized commands. In some embodiments,communicating via short-range communication includes communicating usinga short-range communication protocol.

Displaying various options based on hardware and/or functionality of anelectronic lock provides the user with visual feedback about thecomputer system's ability to configure the electronic lock and enablesthe user to only configure features supported by the electronic lock,thereby reducing the number of required inputs.

In some embodiments, prior to receiving the request (e.g., 650 c) toconfigure the electronic lock, detecting, via the one or more inputdevices, the electronic lock (e.g., as in FIG. 6C) (e.g., via detecting,via a camera of the computer system, a QR corresponding to theelectronic lock and/or via detecting, via short-range (e.g., NFC and/orUW/B) communication, the electronic lock). In response to detecting theelectronic lock (e.g., 658), the computer system (e.g., 600) displays auser interface object (e.g., 618 and/or 618 c) (e.g., an objectcorresponding to the detected QR code), wherein the request to configurethe electronic lock is an input corresponding to (e.g., a tap input on)the user interface object (e.g., 618 c). Displaying the user interfaceobject in response to detecting the electronic lock provides the userwith visual feedback that the electronic lock has been detected by thecomputer system.

In some embodiments, during the configuration process (706) forconfiguring the electronic lock: the computer system (e.g., 600)receives, via the one or more input devices, user input (e.g., 650 d)(e.g., touch input) that selects a location (e.g., a room of a home, aportion (front area, back area) of a home) for the electronic lock; thecomputer system (e.g., 600) associates, based on the user input thatselects the location, the electronic lock with the location; thecomputer system (e.g., 600) receives, via the one or more input devices,user input (e.g., 650 e) that selects a name (e.g., front door lock,side door lock) for the electronic lock; and the computer system (e.g.,600) associates, based on the user input that selects the name, theelectronic lock with the name. Associating the electronic lock with alocation and a name enables the computer system to subsequently identifyand represent that particular electronic lock using the location andname identifiers, thereby reducing the number of inputs the user mustprovide to find a particular electronic lock.

In some embodiments, during the configuration process (706) forconfiguring the electronic lock, the computer system (e.g., 600)displays (e.g., concurrently), via the display generation component, oneor more lock automation options (e.g., 636 a-636 c), which, whenenabled, cause the electronic lock to change to a predefined state(e.g., to lock, to unlock) when a lock condition (e.g., a first lockcondition and/or a second lock condition) is met. Providing the userwith lock automation options during the configuration process enablesthe computer system to automate procedures (e.g., locking of theelectronic lock and/or transmitting instructions to the electroniclock), thereby performing the procedure when the condition is met andreducing the need for the user to provide user input to perform theprocedure.

In some embodiments, a first lock automation option, when enabled (e.g.,via user input), causes the electronic lock to become locked when a userof the computer system has been detected as leaving a location (e.g., ahome) corresponding to the electronic lock. In some embodiments, asecond lock automation option, when enabled (e.g., via user input),causes the electronic lock to become unlocked when a user of thecomputer system has been detected as arriving at (or near) the location(e.g., a home) corresponding to the electronic lock. In someembodiments, a third lock automation option, when enabled (e.g., viauser input), causes the electronic lock to become locked when no usersof a home automation system associated with the location (e.g., home)are detected as being at the location (e.g., when it is detected that alast user of the home automation system has departed the location and noother users of the home automation system remain at the location). Insome embodiments, the one or more lock automation options includes afourth lock automation option in accordance with a determination thatthe electronic lock includes a short-range communication feature forcommunicating via short-range wireless communication and does notinclude the fourth lock automation option in accordance with adetermination that the electronic lock does not include a short-rangecommunication feature for communicating via short-range wirelesscommunication. In some embodiments, the one or more lock automationoptions include a fifth lock automation option in accordance with adetermination that the electronic lock includes a keypad feature anddoes not include the fifth lock automation option in accordance with adetermination that the electronic lock does not include a keypadfeature.

In some embodiments, during the configuration process (706) forconfiguring the electronic lock, in accordance with a determination thata home automation system associated with the computer system (e.g., thecomputer system is a user and/or administrator of the home automationsystem) is configured for guest access (e.g., one or more guests haveaccess to the home automation system, the home automation systemincludes one or more guest accounts), the computer system (e.g., 600)displays, via the display generation component, a user interface (e.g.,638) to enable guests of the home automation system to operate (e.g.,change a state of, lock and/or unlock) the electronic lock, including: afirst guest user interface object (e.g., 638 a) that is selectable(e.g., via tap input) to enable a first guest of the home automationsystem to operate the electronic lock without enabling a second guest ofthe home automation system to operate the electronic lock, and a secondguest user interface object (e.g., 638 b) that is selectable (e.g., viatap input) to enable the second guest to operate the electronic lockwithout enabling the first guest to operate the electronic lock. In someembodiments, during the configuration process (706) for configuring theelectronic lock, in accordance with a determination that the homeautomation system associated with the computer system (e.g., thecomputer system is a user and/or administrator of the home automationsystem) is not configured for guest access (e.g., one or more guestshave access to the home automation system, the home automation systemincludes one or more guest accounts), the computer system (e.g., 600)forgoes displaying, via the display generation component, the userinterface to enable guests of the home automation system to operate(e.g., change a state of, lock and/or unlock) the electronic lock.Displaying a list of guests of the home automation system enables thecomputer system to configure those users' access to the electronic lock,thereby reducing the inputs that would otherwise be required to access aguest configuration interface for this particular electronic lock.

In some embodiments, guests are not enabled to operate the electroniclock by default. In some embodiments, select of a respective guestcauses an indication to be displayed (e.g., adjacent to a respectiveguest user interface objection) indicating that the respective guest hasbeen selected to have access to operate the electronic lock. In someembodiments, the home automation system includes different levels ofaccess, such as a highest level of access for an administrator, a lowerlevel of access for a non-administrators (e.g., standard users), and thelowest level of access for guests (e.g., temporary visitors of the home,users with reduced permissions to configure aspects of the homeautomation system).

In some embodiments, the computer system (e.g., 600) configures theelectronic lock (e.g., by transmitting configuration information to theelectronic lock and/or to one or more devices and/or hubs of the homeautomation system; and/or configuring one or more functions or one ormore settings of the electronic lock) based on user inputs receivedduring the configuration process for configuring the electronic lock. Insome embodiments, the computer system configures the electronic lock bywirelessly transmitting (e.g., via NFC, via UWB, via WiFi) configurationinformation to the electronic lock. The configuration informationoptionally includes information (e.g., account identifiers of usersand/or guests and/or pin codes for unlocking the electronic lock). Insome embodiments, configuring the electronic lock includes transmittingthe code to be used for unlocking the electronic lock to the electroniclock, such that the electronic lock can compare a code received at thekeypad to the code for unlocking.

In some embodiments, subsequent to configuring the electronic lock, thecomputer system (e.g., 600) detects, via one or more input devices, userinput (e.g., 650 q) (e.g., touch input on a touch sensitive surface ofthe computer system) corresponding to a request to transmit, to theelectronic lock, credentials of the first account to unlock theelectronic lock and in response to detecting the request (e.g., 650 q)to transmit credentials of the first account to unlock the electroniclock, the computer system (e.g., 600) transmits, to the electronic lockvia short-range communication (e.g., via NFC, WiFi, and/or UWB),credentials of the first account.

In some embodiments, subsequent to configuring the electronic lock, thecomputer system (e.g., 600) receives (e.g., from a device of the homeautomation system, from the lock itself), via the one or more inputdevices (e.g., via NFC, via UWB, via WiFi), an indication that theelectronic lock has been unlocked using a code associated with aparticular account (e.g., associated with the first account, associatedwith a second account different from the first account) and in responseto receiving the indication that the electronic lock has been unlockedusing the code associated with the particular account, the computersystem (e.g., 600) displays, via the display generation component, anotification (e.g., 664) indicating that the electronic lock has beenunlocked using the code associated with the particular account (e.g., anotification stating “The front door was unlocked using David's code.”).Displaying a notification indicating that the electronic lock has beenunlocked using a code associated with a particular account provides theuser with improved visual feedback about the state of the homeautomation system (a particular user's account was used to unlock anelectronic lock) and the state of the computer system (has detected thata particular user's account was used to unlock an electronic lock).

In some embodiments, subsequent to configuring the electronic lock, thecomputer system (e.g., 600) detects, via the one or more input devices(e.g., via NFC, via UWB), a wireless field of the electronic lock and inresponse to detecting the wireless field of the electronic lock, thecomputer system (e.g., 600) transmits (e.g., as in FIGS. 6S-6T), to theelectronic lock via short-range communication (e.g., via NFC, WiFi,and/or UWB), credentials of the first account (e.g., without requiringauthentication after detecting the wireless field of the electroniclock). In some embodiments, transmitting the credentials of the firstaccount causes the electronic lock to unlock. In some embodiments, thefirst account can be configured on various computer systems (e.g., asmartphone, a smartwatch) associated with the same user, such that thevarious computer systems can use the first account to providecredentials to unlock the electronic lock. Transmitting credentials ofthe first account to the electronic lock in response to detecting awireless field of the electronic lock reduces the number of user inputsrequired to cause an unlock of the device (e.g., by not requiring theuser to navigate to a particular user interface, not requiring the userto select a particular user interface object, and/or not requiring theuser to enter a passcode/password.)

In some embodiments, while displaying, via the display generationcomponent, the option (e.g., 628 a, 654) (e.g., a graphical userinterface object) to configure the first account of the computer systemto provide credentials (e.g., to unlock the electronic lock) viashort-range communication (e.g., via NFC, WiFi, and/or UWB) withoutrequiring authentication, the computer system (e.g., 600) receives, viathe one or more input devices, one or more configuration user inputs(e.g., 650 g, 650 u) selecting the option to configure the first accountof the computer system to provide credentials via short-rangecommunication without requiring authentication. Subsequent to (e.g., inresponse to) receiving the one or more configuration user inputs (e.g.,650 g, 650 u), the computer system (e.g., 600) receives, via the one ormore input devices (e.g., a camera and/or a depth sensor) biometricinformation (e.g., information about a face detected using the one ormore input devices, as indicated in FIG. 6R). In accordance with adetermination that the biometric information matches enrolled biometricinformation (e.g., facial recognition is successful and the computersystem determines that the biometric information received is from anauthorized user), the computer system (e.g., 600) configures the firstaccount of the computer system to provide credentials (e.g., to theelectronic lock) via short-range communication without requiringauthentication (e.g., without requiring the authentication between whenthe electronic lock requests the credentials and when the credentialsare provided, even if the computer system is in a locked state). Inaccordance with a determination that the biometric information does notmatch enrolled biometric information (e.g., facial recognition is notsuccessful and the computer system determines that the biometricinformation received is not from an authorized user), the computersystem (e.g., 600) forgoes configuring the first account of the computersystem to provide credentials (e.g., to the electronic lock) viashort-range communication without requiring authentication. Usingconfirming that biometric information matches enrolled biometricinformation before configuring the first account to provide credentialswithout requiring authentication makes the computer system more secureby preventing an unauthorized user from enabling a feature that unlocksthe electronic lock without requiring authentication.

In some embodiments, configuring the electronic lock includesconfiguring the electronic lock for use as part of a home automationsystem (e.g., the electronic lock is part of the home automationsystem). In some embodiments, subsequent to configuring the electroniclock (e.g., in response to completing configuring the electronic lock),the computer system (e.g., 600) initiates a process to causenotifications to be transmitted to one or more other computer systems(e.g., 666) (other than the computer system) of users of the homeautomation system (e.g., transmitting the notifications to the one ormore other computer systems and/or providing information to a secondcomputer system to transmit the notifications to the one or more othercomputer system) indicating (e.g., 668) that an account of the one ormore other computer systems (e.g., 666) can be configured to providecredentials to the electronic lock via short-range communication withoutrequiring authentication. Causing notifications to be transmitting tocomputer systems of the home automation system provides those users withinformation about the state of the home automation system (that a newlock is operational) and enables those users to configured and/oroperate (e.g., unlock) the electronic lock using their computer system.

In some embodiments, the computer system (e.g., 600) configuring theelectronic lock includes automatically adding the first account (e.g.,an electronic key) to an electronic wallet (e.g., as illustrated in FIG.6P) of the computer system, wherein the electronic wallet includes oneor more additional accounts (e.g., loyalty accounts, transit accountsand/or payment accounts associated with respective credentials).Automatically adding the first account (e.g., an electronic key) to anelectronic wallet of the computer system enables the user of thecomputer system to subsequently access/use the first account.

In some embodiments, adding the first account (e.g., an electronic key)to the electronic wallet of the computer system includes associating thefirst account with a visual representation (e.g., 648 a) (e.g., a cardin the electronic wallet and/or representing a key), wherein a color(e.g., artwork, background) of the visual representation (e.g., 648 a)is selected based on a color of the electronic lock (e.g., 658) (e.g.,the color of the hardware, the color of the handle, and/or the color ofthe mortise cylinder). In some embodiments, in accordance with adetermination that the electronic lock is a first color, a color (e.g.,a background color) of a visual representation of the first account is asecond color (e.g., same as the first color and/or different from thethird color) and in accordance with a determination that the electroniclock is a third color, the color (e.g., a background color) of thevisual representation of the first account is a fourth color (e.g., sameas the third color and/or different from the fourth color). Providingthe user with display of a visual representation with a color that isbased on the color of the electronic lock provides the user with visualfeedback that the first account corresponds to that particularelectronic lock.

Note that details of the processes described above with respect tomethod 700 (e.g., FIG. 7 ) are also applicable in an analogous manner tothe methods described below. For example, method 900 optionally includesone or more of the characteristics of the various methods describedabove with reference to method 700. For example, the electronic lock ofmethod 700 is the same as the first or second electronic lock of method900. For another example, the computer system of method 700 is the sameas the computer system of method 900. For another example, the firstaccount of method 700 is the same as the first account of method 900.For brevity, these details are not repeated below.

FIGS. 8A-8S illustrate exemplary user interfaces for managing access forone or more lock accessories, in accordance with some embodiments. Theuser interfaces in these figures are used to illustrate the processesdescribed below, including the processes in FIG. 9 .

FIG. 8A illustrates electronic device 600 displaying, via display 602,first user interface 604. At FIG. 8A, electronic device 600 detects userinput 850 a (e.g., a tap gesture) corresponding to selection of homeuser interface object 604 a. In response to detecting user input 850 a,electronic device 600 displays home options user interface 802. Homeoptions user interface 802 includes rooms region 802 a, home settingsuser interface object 802 b, room settings user interface object 802 c,and edit user interface object 802 d. In some embodiments, in responseto detecting user input corresponding to rooms region 802 a, electronicdevice 600 displays a room user interface corresponding to one or moreaccessory devices designated as being positioned within a respectiveroom of the home automation system. In some embodiments, in response todetecting user input corresponding to room settings user interfaceobject 802 c, electronic device 600 displays a room settings userinterface that enables electronic device 600 to create a room, remove aroom, designate one or more accessory devices to a room, and/or remove adesignation of one or more accessory devices from a room. In someembodiments, in response to detecting user input corresponding to edituser interface object 802 d, electronic device 600 displays an editinguser interface for adjusting and/or changing an appearance and/or layoutof first user interface 604.

At FIG. 8A, electronic device 600 detects user input 850 b (e.g., a tapgesture) corresponding to selection of home settings user interfaceobject 802 b. In response to detecting user input 850 b, electronicdevice 600 displays home settings user interface 804, as shown at FIG.8B.

At FIG. 8B, home settings user interface 804 includes home indicator 804a (e.g., ‘Home’) corresponding to an identifier and/or name of the homeassociated with the home automation system, user region 806, settingsregion 808, and software update user interface object 804 b. In someembodiments, in response to detecting user input selecting softwareupdate user interface object 804 b, electronic device 600 is configuredto cause one or more accessory devices (e.g., ‘Speaker’) of the homeautomation system to update a software program of the one or moreaccessory devices.

At FIG. 8B, settings region 808 includes cameras and doorbells userinterface object 808 a corresponding to settings of one or more cameraaccessory devices and/or doorbell accessory devices of the homeautomation system, intercom user interface object 808 b corresponding tointercom settings of the home automation system, sensors user interfaceobject 808 c corresponding to settings of one or more sensor accessorydevices of the home automation system, and locks user interface object808 d corresponding to settings of one or more lock accessory devices ofthe home automation system. As set forth below with reference to FIGS.8M-8P, electronic device 600 displays lock settings user interface 848in response to detecting user input 850 c (e.g., a tap gesture)correspond to selection of locks user interface object 808 d.

User region 806 of home settings user interface 804 corresponds to usersthat have access and/or authorization to one or more accessory devicesof the home automation system. At FIG. 8B, user region 806 includesresident user interface objects 806 a-806 c, guest user interface object806 d, and add user interface object 806 e. Resident user interfaceobjects 806 a-806 c correspond to respective users that have beendesignated as residents of the home associated with the home automationsystem (e.g., individuals that reside and/or live at the home). In someembodiments, users that are designated as residents of the home haveaccess and/or authorization to all accessory devices of the homeautomation system. In some embodiments, users that are designated asresidents of the home have access and/or authorization to a set ofaccessory devices for which users designated as guests do not haveaccess and/or authorization.

At FIG. 8B, guest user interface object 806 d corresponds to usersdesignated as guests of the home associated with the home automationsystem (e.g., individuals that do not reside and/or live at the home).Guest user interface object 806 d indicates that the home includes threeusers (e.g., ‘3 People’) that have been designated as guests of thehome. Therefore, at FIG. 8B, electronic device 600 groups usersdesignated as guests together and displays guest user interface object806 d corresponding to the group of users designated as guests. In someembodiments, in response to detecting user input selecting guest userinterface object 806 d, electronic device 600 displays respective guestuser interface objects corresponding to each guest of the home. In someembodiments, electronic device 600 displays respective user interfaceobjects for users designated as guests on home settings user interface804. In some embodiments, users designated as guests have limited accessand/or authorization to one or more particular accessory devices of thehome automation system. In other words, because users designated asguests do not reside at the home, users designated as guests do not haveaccess and/or authorization to some types of accessory devices, such aslights, speakers and/or televisions.

As set forth below, electronic device 600 is configured to initiate aprocess for adding a new user (e.g., a resident and/or a guest) inresponse to detecting user input corresponding to add user interfaceobject 806 e. At FIG. 8B, electronic device 600 detects user input 850 d(e.g., a tap gesture) corresponding to selection of add user interfaceobject 806 e. In response to detecting user input 850 d, electronicdevice 600 displays add user interface 838, as shown at FIG. 8J.

Alternatively, at FIG. 8B, electronic device 600 detects user input 850e (e.g., a tap gesture) corresponding to selection of first residentuser interface object 806 a (e.g., ‘John Appleseed’). In response todetecting user input 850 e, electronic device 600 displays user settingsuser interface 810, as shown at FIG. 8C.

At FIG. 8C, user settings user interface 810 includes user informationregion 810 a including a name, an identifier, and/or contact informationassociated with the resident user corresponding to first resident userinterface object 806 a (e.g., ‘John Appleseed’). User settings userinterface 810 also includes settings region 812, media user interfaceobject 810 b, access region 814, and accessories region 816.

At FIG. 8C, settings region 812 includes assistant user interface object812 a for enabling and/or disabling an electronic assistant for theresident user (e.g., an electronic assistant that responds to voicecommands of the resident user (e.g., based on voice recognition of theresident user) received via a microphone of an external device (e.g., asmart speaker)), requests user interface object 812 b for enablingand/or disabling assistant requests that are customized to the residentuser (e.g., the electronic assistant responding to voice commands with acustomized name of the resident user associated with first resident userinterface object 806 a), and television user interface object 812 c fordisplaying a user interface object corresponding to the resident user ona television of the home automation system.

In some embodiments, in response to detecting user input selecting musicinterface object 810 b, electronic device 600 enables the user ofelectronic device 600 to select a music application and/or a playlistthat is available for playback by the resident user (e.g., via anexternal device different from electronic device 600) on one or morespeakers of the home automation system.

Access region 814 includes remote access user interface object 814 acorresponding to whether an external device of the resident user (e.g.,an electronic device different from electronic device 600) is enabled tocause one or more accessory devices of the home automation to transitionbetween modes. At FIG. 8C, access region 814 includes edit accessoriesuser interface object 814 b corresponding to whether the external deviceof the resident user is enabled to add new accessory devices, removeaccessory devices, and/or adjust one or more settings of accessorydevices of the home automation system.

At FIG. 8C, accessories region 816 includes cameras user interfaceobject 816 a corresponding to one or more camera accessory devices ofthe home automation system and locks user interface object 816 bcorresponding to one or more lock accessory devices of the homeautomation system. In some embodiments, in response to detecting userinput selecting cameras user interface object 816 a, electronic device600 displays a camera settings user interface, which corresponds toenabling and/or disabling access and/or authorization for the residentuser with respect to the one or more camera accessory devices of thehome (e.g., whether the resident user has access to view images capturedvia the one or more camera accessory devices of the home).

At FIG. 8C, electronic device 600 detects user input 850 f (e.g., a tapgesture) corresponding to selection of locks user interface object 816b. In response to detecting user input 850 f, electronic device 600displays lock settings user interface 818, as shown at FIG. 8D.

At FIG. 8D, lock settings user interface 818 corresponds to accessand/or settings for one or more lock accessory devices of the homeautomation system, where the access and/or settings are specific to theresident user associated with first resident user interface object 806 a(e.g., ‘John Appleseed’). In other words, in response to detecting userinput on one or more user interface objects of lock settings userinterface 818, electronic device 600 is configured to adjust accessand/or settings for the one or more lock accessories of the homeautomation system for the resident user associated with first residentuser interface object 806 a, but electronic device 600 does not adjustaccess and/or settings for the one or more lock accessories of the homeautomation system for other users (e.g., users associated with residentuser interface objects 806 b-806 c and/or users associated with guestuser interface object 806 d).

Lock settings user interface 818 includes notifications user interfaceobject 818 a, access region 820, and pin region 822. In someembodiments, in response to detecting user input selecting notificationsuser interface object 818 a, electronic device 600 is configured tomanage whether electronic device 600 displays notifications associatedwith the resident user (e.g., ‘John Appleseed’) causing one or more lockaccessory devices of the home automation system to transition betweenmodes (e.g., between the locked mode and the unlocked mode).

Access region 820 of lock settings user interface 818 includes firstlock user interface object 820 a corresponding to a front door lock ofthe home automation system and second lock user interface object 820 bcorresponding to a garage door lock of the home automation system. AtFIG. 8D, first lock user interface object 820 a and second lock userinterface object 820 b are both in an active and/or on positionindicating that the resident user associated with first resident userinterface object 806 a has access to both the front door lock and thegarage door lock. As such, in some embodiments, the resident userassociated with first resident user interface object 806 a is able tocause both the front door lock and the garage door lock to transitionbetween modes via an external device and/or via a pin associated withthe resident user.

At FIG. 8D, electronic device 600 detects user input 850 g (e.g., a tapgesture) corresponding to selection of first lock user interface object820 a. In response to detecting user input 850 g, electronic device 600initiates a process (e.g., communicates with the front door lock and/ora server) to revoke the resident user's access to the front door lock.

At FIG. 8E, electronic device 600 displays first lock user interfaceobject 820 a in a disabled and/or off position indicating that theresident user associated with first resident user interface object 806 ano longer has access to the front door lock. In other words, theresident user associated with first resident user interface object 806 acannot use an external device and/or a pin associated with the residentuser to cause the front door lock to transition between modes (e.g., tounlock).

At FIG. 8E, pin region 822 of lock settings user interface 818 includespin user interface object 822 a corresponding to a pin that the residentuser can enter into a keypad of the garage door lock to cause the garagedoor lock to transition between modes (and, optionally, the front doorlock when first lock user interface object 820 a is in the enabledand/or on mode). Pin region 822 also includes change pin user interfaceobject 822 b, which enables electronic device 600 to change the pin(e.g., the pin displayed on pin user interface object 822 a) that theresident user can enter into the keypad of the garage door lock to causethe garage door lock to transition between modes.

For instance, at FIG. 8E, electronic device 600 detects user input 850 h(e.g., a tap gesture) corresponding to selection of change pin userinterface object 822 b. In response to detecting user input 850 h,electronic device 600 displays change pin user interface 632, as shownat FIG. 8F.

At FIG. 8F, change pin user interface 632 includes pin indicator 632 a,keyboard 632 b, and done user interface object 632 c. At FIG. 8F,computer system 600 has detected one or more user inputs correspondingto keyboard 632 b and displays pin 824 (e.g., ‘6788’) in pin indicator632 a. As such, change pin user interface 632 allows a user to input aunique pin that electronic device 600 associates with the resident user(e.g., ‘John Appleseed’) and enables for use with the garage door lock(e.g., electronic device 600 communicates with the garage door lock overa wireless communication to cause the garage door lock to accept the pinas authorization for transitioning the garage door lock between modes).At FIG. 8F, electronic device 600 detects user input 850 i (e.g., a tapgesture) corresponding to selection of done user interface object 632 c.In response to detecting user input 850 i, electronic device 600displays (e.g., re-displays) lock settings user interface 818, as shownat FIG. 8G.

At FIG. 8G, electronic device 600 displays pin 824 in pin user interfaceobject 822 a indicating that the pin associated with the resident user(e.g., ‘John Appleseed’) has been changed (e.g., from ‘4567’ to ‘6788’).In some instances, the user of electronic device 600 is not within aproximity to the resident user to provide the new pin to the residentuser (e.g., orally and/or via a physical note). As such, electronicdevice 600 is configured to share the new pin with the resident user viaan external device of the resident user. In some embodiments, theexternal device of the resident user displays a notificationcorresponding to the new pin after the pin has been changed viaelectronic device 600 (e.g., regardless of whether electronic device 600shares the new pin with the resident user or not).

At FIG. 8G, electronic device 600 detects user input 850 j (e.g., a tapgesture and/or a long press gesture) corresponding to selection of pinuser interface object 822 a. In response to detecting user input 850 j,electronic device 600 displays share user interface 826, as shown atFIG. 8H.

At FIG. 8H, share user interface 826 includes user selection region 830,sharing options region 832, and copy user interface object 826 a. Userselection region 830 includes contact user interface objects 830 a-830 dcorresponding to respective contact information (e.g., phone numbers,email addresses, and/or usernames) for users stored by and/or otherwiseaccessible to electronic device 600. In some embodiments, in response todetecting user input corresponding to one of contact user interfaceobjects 830 a-830 d, electronic device 600 selects the respectivecontact information for sharing the pin with a respective user. In someembodiments, electronic device 600 includes contact information for theresident user and selects the contact information for the resident userfor sharing the pin with the resident user in response to detecting userinput 850 j (e.g., and without detecting user input corresponding to oneof contact user interface objects 830 a-830 d).

Sharing options region 832 includes sharing option user interfaceobjects 832 a-832 d corresponding to different communication protocolsfor sharing the pin with the resident user. First sharing option userinterface object 832 a corresponds to a short-range communicationtechnique (e.g., Bluetooth, Wi-Fi, and/or Zigbee) for sharing the pinwith the resident user (e.g., an external device associated with theresident user). Second sharing option user interface object 832 bcorresponds to a first messaging application that enables electronicdevice 600 to share the pin with the resident user via an electronicmessage (e.g., a short message service message). Third sharing optionuser interface object 832 c corresponds to an email application thatenables electronic message to share the pin with the resident user viaan email. Fourth sharing option user interface object 832 d correspondsto a second messaging application that enables electronic device 600 toshare the pin with the resident user via an electronic message (e.g., ashort message service message and/or an instant message).

At FIG. 8H, in response to detecting user input selecting copy userinterface object 826 a, electronic device 600 copies (e.g., stores dataassociated with) the pin, such that electronic device 600 can laterreproduce (e.g., paste) the pin in response to one or more additionaluser inputs. In some embodiments, electronic device 600 copies the pinin response to detecting user input 850 j. In some such embodiments,electronic device 600 forgoes displaying copy user interface object 826a on sharing user interface 826.

At FIG. 8H, electronic device 600 detects user input 850 k (e.g., a tapgesture) corresponding to selection of second sharing option userinterface object 832 b. In response to detecting user input 850 k,electronic device 600 displays a messaging user interface correspondingto the first messaging application associated with second sharing optionuser interface object 832 b. The messaging user interface enables a userof electronic device 600 to send the pin (and, optionally, a custommessage with the pin) to the resident user via an electronic message.

FIG. 8I illustrates electronic device 834 associated with the residentuser (e.g., ‘John Appleseed’) displaying, via display 834 a,notification 836. Notification 836 includes indicator 836 a, whichprovides an indication to the resident user that the pin associated withthe resident user has been changed (e.g., by the user of electronicdevice 600). In some embodiments, electronic device 834 displaysnotification 836 in response to receiving an indication (e.g., fromelectronic device 600 and/or from another external device, such as aserver) that the pin has been changed regardless of whether electronicdevice 600 shares the pin with the resident user via sharing userinterface 826. In some such embodiments, electronic device 834 displaysthe new pin (e.g., ‘6788’) in response to detecting user input selectingnotification 836, such that the resident user can view the new pin anduse the new pin to cause the garage door lock to transition betweenmodes.

As set forth above, in response to detecting user input 850 dcorresponding to selection of add user interface object 806 e of homesettings user interface 804, electronic device 600 displays add userinterface 838, as shown at FIG. 8J.

At FIG. 8J, add user interface 838 corresponds to adding a new user tothe home automation system, where the user can be granted various levelsof access to the accessories of the home automation system viaelectronic device 600. Add user interface 838 includes administratoruser interface object 838 a, resident user interface object 838 b, andguest user interface object 838 c. In some embodiments, a new userdesignated as an administrator via user input corresponding toadministrator user interface object 838 a is more access as compared tonew users designated as a resident (e.g., via user input correspondingto selection of resident user interface object 838 b) and/or a guest(e.g., via user input corresponding to selection of guest user interfaceobject 838 c). In some embodiments, a new user designated as a residentvia user input corresponding to resident user interface object 838 b isgranted more access than a new user designated as a guest (e.g., viauser input corresponding to selection of guest user interface object 838c).

At FIG. 8J, electronic device 600 detects user input 850 l (e.g., a tapgesture) corresponding to selection of resident user interface object838 b. In response to detecting user input 850 l, electronic device 600displays add resident user interface 840, as shown at FIG. 8K.Alternatively, at FIG. 8J, electronic device 600 detects user input 850m (e.g., a tap gesture) corresponding to selection of guest userinterface object 838 c. In response to detecting user input 850 m,electronic device 600 displays add guest user interface 842, as shown atFIG. 8L. In some embodiments, in response to detecting user inputselecting administrator user interface object 838 a, electronic device600 displays add resident user interface 840 and/or a similar userinterface to add resident user interface 840.

At FIG. 8K, add resident user interface 840 includes contact userinterface objects 840 a-840 c corresponding to users designated asfamily members of a user associated with electronic device 600 (e.g.,designated as family members via an account of electronic device 600).In some embodiments, electronic device 600 suggests adding users thatare designated as family members because family members are likely toreside in the same home as the user of electronic device 600. In someembodiments, in response to detecting user input selecting one ofcontact user interface objects 840 a-840 c, electronic device 600displays a second add resident user interface that resembles add guestuser interface 842, as shown at FIG. 8L (e.g., the second add residentuser interface displays the name of the user corresponding to theselected contact user interface object 840 a-840 c and, optionally,indicates the user has access to all lock accessories of the homeautomation system).

At FIG. 8L, add guest user interface 842 includes name user interfaceobject 842 a, access region 844, and pin region 846. In someembodiments, in response to detecting user input selecting name userinterface object 842 a, electronic device 600 displays a keyboard (e.g.,a virtual keyboard) that enables a user to input (e.g., type) a nameassociated with the new user. In some embodiments, when electronicdevice 600 detects user input selecting resident user interface object838 b and displays the second add resident user interface, electronicdevice 600 displays a name in name user interface object 842 a thatcorresponds to a selected contact user interface object 840 a-840 c(e.g., without detecting user input on the keyboard).

Similar to lock settings user interface 818, access region 844 includesfirst lock user interface object 844 a corresponding to the front doorlock of the home automation system and second lock user interface object844 b corresponding to the garage door lock of the home automationsystem. At FIG. 8L, first lock user interface object 844 a is in anenabled and/or on position indicating that the new user currently hasand/or will have access to the front door lock of the home automationsystem. In contrast, second lock user interface object 844 b is in thedisabled and/or off position indicating that the new user currently doesnot and/or will not have access to the garage door lock of the homeautomation system. In some embodiments, electronic device 600 isconfigured to transition first lock user interface object 844 a and/orsecond lock user interface object 844 b between the enabled and disabledpositions in response to detecting user input selecting first lock userinterface object 844 a and/or second lock user interface object 844 b.As such, a user can select particular lock accessories for which togrant the new user access.

Pin region 846 includes pin user interface object 846 a including pin846 b and change pin user interface object 846 c. As set forth abovewith reference to FIGS. 8E-8H, in some embodiments, electronic device600 is configured to share pin 846 b with the new user and/or change pin846 b in response to detecting user input selecting pin user interfaceobject 846 a and/or change pin user interface object 846 c,respectively. In some embodiments, when both first lock user interfaceobject 844 a and second lock user interface object 844 b are in theenabled and/or on position, the guest user (e.g., ‘Dog Walker’) can usepin 846 b to unlock both the front door lock and the garage door lock.At FIG. 8L, the guest user can use pin 846 b to unlock the front doorlock but not the garage door lock because second lock user interfaceobject 844 b is in the disabled and/or off position.

In some embodiments, pin region 846 includes a scheduling user interfaceobject that, when selected via user input, enables the user ofelectronic device 600 to set particular times (e.g., time of day, daysof the week, days of the month, and/or months of the year) for which pin846 b is authorized to cause front door lock (and/or the garage doorlock) to transition between modes. In some such embodiments, electronicdevice 600 communicates with the front door lock, so that the front doorlock is configured to accept pin 846 b at the particular times, but tonot accept pin 846 b at other times. For instance, in some embodiments,electronic device 600 detects one or more user inputs causing electronicdevice 600 to enable pin 846 b associated with the guest user (e.g.,‘Dog Walker’) to be valid for use between 12 pm and 1 pm on Mondays,Wednesdays, and Fridays. When the guest user (e.g., ‘Dog Walker’)attempts to enter pin 846 b to cause the front door lock to transitionbetween modes at 3 pm on a Tuesday, the front door lock will nottransition between modes (and, optionally, electronic device 600displays a notification related to the front door lock receiving pin 846b associated with the guest user outside of the scheduled time).

As set forth above, in response to detecting user input 850 ccorresponding to selection of locks user interface object 806 d of homesettings user interface 804, electronic device 600 displays locksettings user interface 848, as shown at FIG. 8M.

At FIG. 8M, lock settings user interface 848 includes notifications userinterface object 848 a, lock region 852 corresponding to lock accessorydevices of the home automation system, and user region 854 correspondingto users having access to at least one lock accessory device of the homeautomation system. In some embodiments, in response to detecting userinput selecting notifications user interface object 848 a, electronicdevice 600 displays a notification user interface that enables a user ofelectronic device 600 to adjust one or more notification settingsassociated with lock accessory devices of the home automation system(e.g., notification settings corresponding to whether electronic device600 displays notifications in response to detecting and/or receiving anindication associated with an event (e.g., an unlock event, a lockevent, and/or a change pin event) of the one or more lock accessorydevices).

At FIG. 8M, lock region 852 includes first lock user interface object852 a corresponding to the front door lock of the home automation systemand second lock user interface object 852 b corresponding to the garagedoor lock of the home automation system. As set forth below, in responseto detecting user input 850 n (e.g., a tap gesture) corresponding toselection of first lock user interface object 852 a, electronic device600 displays first lock settings user interface 856 corresponding tosettings associated with the front door lock (e.g., and not settingsassociated with the garage door lock). In some embodiments, in responseto detecting user input corresponding to selection of second lock userinterface object 852 b, electronic device 600 displays a second locksettings user interface corresponding to settings associated with thegarage door lock (e.g., and not settings associated with the front doorlock).

At FIG. 8M, user region 854 includes first user interface object 854 acorresponding to a first resident user of the home automation system(e.g., ‘John Appleseed), second user interface object 854 bcorresponding to a second resident user of the home automation system(e.g., ‘Jane Appleseed’), third user interface object 854 ccorresponding to a third resident user of the home automation system(e.g., ‘Sam Appleseed’), and guest user interface object 854 dcorresponding to three guest users of the home automation system (e.g.,as indicate by ‘Guest 3 People’ on guest user interface object 854 d).Electronic device 600 displays individual user interface objects foreach resident user of the home automation system and a single userinterface object corresponding to all of the guest users of the homeautomation system.

In some embodiments, in response to detecting user input correspondingto selection of first user interface object 854 a, electronic device 600displays lock settings user interface 818 corresponding to the firstresident user (e.g., ‘John Appleseed’). In some embodiments, in responseto detecting user input corresponding to selection of one of second userinterface object 854 b and third user interface object 854 c, electronicdevice 600 displays a lock settings user interface corresponding to thesecond resident user and the third resident user, respectively. In someembodiments, in response to detecting user input corresponding toselection of guest user interface object 854 d, electronic device 600displays a guest user interface including three guest user interfaceobjects corresponding to each of the three guests. In some embodiments,in response to detecting user input selecting a guest user interfaceobject of the guest settings user interface, electronic device 600displays a guest settings user interface corresponding to the respectiveguest associated with the selected guest user interface object.

At FIG. 8M, electronic device 600 detects user input 850 n (e.g., a tapgesture) corresponding to selection of first lock user interface object852 a. In response to detecting user input 850 n, electronic devicedisplays first lock settings user interface 856, as shown at FIG. 8N.

At FIG. 8N, first lock settings user interface 856 corresponds tosettings associated with the front door lock and does not correspond tosettings associated with other lock accessories of the home automationsystem (e.g., the garage door lock). First lock settings user interface856 includes information region 858 including accessory indicator 858 a(e.g., ‘Lock’), accessory location indicator 858 b (e.g., ‘Front Door’),and accessory designation indicator 858 c. In some embodiments, inresponse to detecting user input selecting accessory designationindicator 858 c (e.g., a user interface object of accessory designationindicator 858 c), electronic device 600 is configured to designateand/or remove a designation of the front door lock as a favoriteaccessory (e.g., such that electronic device 600 displays and/or doesnot display lock accessory user interface object 640 on first userinterface 604).

At FIG. 8N, first lock settings user interface 856 includes automationsregion 860 including automation user interface objects 860 a-860 c. Insome embodiments, electronic device 600 is configured to enable,disable, and/or add automation settings for the front door lock inresponse to detecting user input selecting one of automation userinterface objects 860 a-860 c. For example, in response to detectinguser input selecting automation user interface object 860 a, electronicdevice 600 disables an automation setting that includes electronicdevice 600 causing the front door lock to transition to a locked modewhen no devices associated with resident users of the home automationsystem are within a predefined distance from the home.

First lock settings user interface 856 includes manage access userinterface object 862, notifications user interface object 864, and lockdetails region 866. In some embodiments, in response to detecting userinput selecting notifications user interface object 864, electronicdevice 600 displays a front door lock notifications user interface thatenables a user to adjust notification settings for the front door lock(e.g., and not adjust notification settings for other lock accessorydevices of the home automation system). Lock details region 866 includesmanufacturer indicator 866 a, serial number indicator 866 b, and modelindicator 866 c, which provide additional details to a user ofelectronic device 600 about the front door lock.

At FIG. 8N, electronic device 600 detects user input 850 o (e.g., a tapgesture) corresponding to selection of manage access user interfaceobject 862. In response to detecting user input 850 o, electronic device600 displays access user interface 868, which corresponds to accesssettings for the front door lock (e.g., and not access settings forother lock accessories of the home automation system), as shown at FIG.8O.

At FIG. 8O, access user interface 868 includes resident region 870 andguest region 872. Resident region 870 includes resident user interfaceobjects 870 a-870 c corresponding to resident users of the homeautomation system and indicating the access for the respective residentusers for the front door lock. Similarly, guest region 872 includesguest user interface objects 872 a-872 c corresponding to guest users ofthe home automation system and indicating the access for the respectiveguest users for the front door lock. At FIG. 8O, guest user interfaceobjects 872 a-872 c displayed in guest region 872 include pin indicators873 corresponding to respective pins for each of the guest users of thehome automation system. In contrast, resident user interface objects 870a-870 c do not include pin indicators 873. In some embodiments,electronic device 600 displays pin indicators 873 for guest userinterface objects 872 a-872 c because guest users of the home automationsystem do not otherwise have access to their pins. In some suchembodiments, electronic device 600 displays pin indicators 873 for guestuser interface objects 872 a-872 c on access user interface 868 so thata user of electronic device 600 can quickly and efficiently provide apin to a respective guest user. In some embodiments, electronic devicesassociated with users of the home automation system that are designatedas administrators receive notifications (and/or are configured toreceive notifications) when a guest pin (e.g., represented by pinindicators 873) is used to cause a lock accessory device of the homeautomation system to transition between modes.

At FIG. 8O, each of the resident users and each of the guest userscurrently have access to the front door lock (e.g., as indicated byresident user interface objects 870 a-870 c and guest users interfaceobjects 872 a-872 c being in an active and/or on position). In someembodiments, in response to detecting user input corresponding to one ofresident user interface objects 870 a-870 c and/or one of guest userinterface objects 872 a-872 c, electronic device 600 initiates a processto revoke access to the front door lock for the respective user (e.g., aresident user and/or a guest user). At FIG. 8O, access user interface868 includes add guest user interface object 874 in guest region 872,which, when selected via user input, enables electronic device 600 toadd a new guest user to the home automation system (e.g., electronicdevice 600 displays add guest user interface 842, as shown at FIG. 8L).

At FIG. 8O, electronic device 600 detects user input 850 p (e.g., a tapgesture and/or a long press gesture) corresponding to guest userinterface object 872 c (e.g., ‘Dog Walker’). In response to detectinguser input 850 p, electronic device 600 displays guest user interface876, as shown at FIG. 8P.

At FIG. 8P, guest user interface 876 includes name user interface object876 a, access region 878, pin region 880, and remove guest userinterface object 876 b. In some embodiments, in response to detectinguser input selecting name user interface object 876 a, electronic device600 displays a keyboard (e.g., a virtual keyboard) that enables a userto modify and/or change (e.g., type) a name associated with the guestuser. In some embodiments, guest user interface 876 includes anotifications user interface object that enables electronic device 600to manage notifications that are generated and/or otherwise displayed byelectronic device 600 and are related to the guest user. For example, insome embodiments, in response to detecting user input selectingnotifications user interface object, electronic device 600 enablesnotifications to be displayed when pin 880 b associated with the guestuser is used to cause the front door lock (and/or the garage door lock)to transition between modes. Similarly, in some embodiments, in responseto detecting user input selecting notifications user interface object,electronic device 600 disables notifications associated with pin 880 bbeing used to cause the front door lock (and/or the garage door lock) totransition between modes.

Access region 878 includes first lock user interface object 878 acorresponding to the front door lock of the home automation system andsecond lock user interface object 878 b corresponding to the garage doorlock of the home automation system. At FIG. 8P, first lock userinterface object 878 a is in an enabled and/or on position indicatingthat the guest user currently has access to the front door lock of thehome automation system. In contrast, second lock user interface object878 b is in the disabled and/or off position indicating that the guestuser currently does not have access to the garage door lock of the homeautomation system. In some embodiments, electronic device 600 isconfigured to transition first lock user interface object 878 a and/orsecond lock user interface object 878 b between the enabled and disabledpositions in response to detecting user input selecting first lock userinterface object 878 a and/or second lock user interface object 878 b.As such, a user can select particular lock accessory devices for whichto grant the guest user access.

Pin region 880 includes pin user interface object 880 a including pin880 b and change pin user interface object 880 c. As set forth abovewith reference to FIGS. 8E-8H, in some embodiments, electronic device600 is configured to share pin 880 b with the guest user and/or changepin 880 b in response to detecting user input selecting pin userinterface object 880 a and/or change pin user interface object 880 c,respectively. In some embodiments, when both first lock user interfaceobject 878 a and second lock user interface object 878 b are in theenabled and/or on position, the guest user (e.g., ‘Dog Walker’) can usepin 880 b to unlock both the front door lock and the garage door lock.At FIG. 8P, the guest user can use pin 880 b to unlock the front doorlock but not the garage door lock because second lock user interfaceobject 878 b is in the disabled and/or off position. As set forth above,in some embodiments, pin region 880 includes a scheduling user interfaceobject that, when selected via user input, enables the user ofelectronic device 600 to set particular times (e.g., time of day, daysof the week, days of the month, and/or months of the year) for which pin880 b is authorized to cause front door lock (and/or the garage doorlock) to transition between modes.

At FIG. 8P, electronic device 600 detects user input 850 q (e.g., a tapgesture) corresponding to selection of remove guest user interfaceobject 876 b. In response to detecting user input 850 q, electronicdevice 600 initiates a process for removing the guest user (e.g., ‘DogWalker’) from the home automation system. In some embodiments, theprocess for removing the guest user from the home automation systemincludes revoking the guest user's access to all lock accessory devicesof the home automation system and/or all accessory devices of the homeautomation system. In some embodiments, electronic device 600 displays aconfirmation user interface in response to detecting user input 850 q,such that electronic device 600 removes the guest user from the homeautomation system in response to additional input corresponding to theconfirmation user interface.

FIGS. 8Q-8S illustrate exemplary user interfaces that includenotifications corresponding to one or more lock accessory devices of thehome automation system. At FIG. 8Q, electronic device 882 of the guestuser (e.g., ‘Dog Walker’) displays, via display 882 a, key disablednotification 884 indicating that an electronic key for accessing thefront door lock of the home automation system has been disabled and/orrevoked (e.g., via user input 850 q at FIG. 8P). At FIG. 8Q, electronicdevice 882 displays key disabled notification 884 on lock user interface886. In some embodiments, electronic device 882 displays key disablednotification 884 while electronic device 882 is in an unlocked state anddisplaying another user interface.

At FIG. 8R, electronic device 882 displays pin removal notification 888indicating that pin 880 b of the guest user (e.g., ‘Dog Walker’) hasbeen removed. In other words, pin removal notification 888 indicates tothe guest that pin 880 b can no longer be utilized to cause the frontdoor lock (and, optionally, other lock accessory devices of the homeautomation system) to transition between modes. In some embodiments,electronic device 882 displays pin removal notification 888 in responseto receiving an indication that the guest was removed from the homeautomation system (e.g., via user input 850 q). In some embodiments,electronic device 882 displays pin removal notification 888 in responseto receiving an indication that the guest's access to at least one lockaccessory device of the home automation system was revoked (e.g., viauser input selecting one of first lock user interface object 878 aand/or second lock user interface object 878 b). At FIG. 8R, electronicdevice 882 displays pin removal notification 888 on lock user interface886. In some embodiments, electronic device 882 displays pin removalnotification 888 while electronic device 882 is in an unlocked state anddisplaying another user interface. In some embodiments, after displayingpin removal notification 888, when the guest user (e.g., ‘Dog Walker’)attempts to enter pin 880 b into a keypad of a lock accessory device ofthe home automation system, the lock accessory device will nottransition between modes because pin 880 b is no longer valid for use.In some embodiments, in response to detecting and/or receiving anindication that the guest user attempted to use pin 880 b after theguest user was removed from the home automation system, electronicdevice 600 displays a notification that alerts the user of electronicdevice 600 that the guest user attempted to use pin 880 b withoutauthorization.

At FIG. 8S, electronic device 600 displays keypad disabled notification890 corresponding to the front door lock of the home automation system.In some embodiments, electronic device 600 detects and/or receives anindication that the keypad for the front door lock has been disabled.For instance, in some embodiments, the front door lock is a batteryoperated lock. When the batteries of front door lock can no longersupply power to the front door lock, electronic device 600 receives anindication that the keypad of the front door lock cannot be used tocause the front door lock to transition between modes, and electronicdevice 600 displays keypad disabled notification 890. In someembodiments, electronic device 600 (and/or electronic device 882)displays keypad disabled notification 890 in response to detectingand/or receiving an indication that a communication connection with thefront door lock (e.g., via a Wi-Fi connection) has been interrupted. Insome embodiments, electronic devices associated with guest users (e.g.,electronic device 882) does not display keypad disabled notification 890and electronic devices associated with resident users (e.g., electronicdevice 600) do display keypad disabled notification 890. At FIG. 8S,electronic device 600 displays keypad disabled notification 890 on lockuser interface 886. In some embodiments, electronic device 600 displayskeypad disabled notification 890 while electronic device 600 is in anunlocked state and displaying another user interface.

FIG. 9 is a flow diagram illustrating a method for managing access forone or more lock accessories using a computer system in accordance withsome embodiments. Method 900 is performed at a computer system (e.g., asmartphone, a tablet, and/or a smartwatch) that is in communication with(e.g., wirelessly or by wire, and/or integrates or includes) a displaygeneration component (e.g., a display or touch-sensitive display) andone or more input devices (e.g., a touch-sensitive surface and/or akeyboard). Some operations in method 900 are, optionally, combined, theorders of some operations are, optionally, changed, and some operationsare, optionally, omitted.

As described below, method 900 provides an intuitive way for managingaccess for one or more lock accessories. The method reduces thecognitive burden on a user for managing access for one or more lockaccessories, thereby creating a more efficient human-machine interface.For battery-operated computing devices, enabling a user to manage accessfor one or more lock accessories faster and more efficiently conservespower and increases the time between battery charges.

The computer system (e.g., 600) displays (902), via the displaygeneration component, an account user interface (e.g., 810, 838) thatincludes a user account lock object (e.g., 816 b, 838 c).

While displaying the user account lock object (e.g., 816 b, 838 c), thecomputer system (e.g., 600) receives (904), via the one or more inputdevices, a first input (e.g., 850 f, 850 m) (e.g., a tap input, a buttonpress) corresponding to selection of the user account lock object (e.g.,816 b, 838 c).

In response to receiving the first input, the computer system (e.g.,600) displays (906) (e.g., by replacing display of the account userinterface), via the display generation component, a user account lockuser interface (e.g., 818, 842) corresponding to a first account,wherein the user account lock user interface includes concurrent displayof: a first electronic lock object (908) (e.g., “FRONT DOOR” of 820 and844), a first status object (910) (e.g., 820 a, 844 a) (e.g., a toggleobject) that indicates whether the first electronic lock is configuredto unlock using credentials (e.g., a pin code entered at the firstelectronic lock by a user and/or a credential transmitted to the firstelectronic lock by the computer system) of the first account, a secondelectronic lock object (912) (e.g., “GARAGE” of 820 and 846), and asecond status object (914) (e.g., 820 b, 844 b) that indicates whetherthe second electronic lock is configured to unlock using credentials ofthe first account. The first electronic lock object (e.g., 820 a)corresponds to a first electronic lock (e.g., a home front door lockthat includes a short-range communication feature for communicating viashort-range wireless communication (e.g., a near field communication(NFC) reader, WiFi, and/or UWB) and a keypad feature (e.g., a numericand/or alphanumeric keypad and/or is configurable to display a numericand/or alphanumeric keypad)) that is separate from (e.g., that is notphysically integrated into the computer system; that does not power on(or off) when the computer system is powered on (or off)) the computersystem. In some embodiments, the computer system is in communication(e.g., wireless communication) with the first electronic lock. Thesecond electronic lock object corresponds to a second electronic lock(e.g., a home side door lock that includes a short-range communicationfeature for communicating via short-range wireless communication (e.g.,a near field communication (NFC) reader, WiFi, and/or UWB) and a keypadfeature (e.g., a numeric and/or alphanumeric keypad and/or isconfigurable to display a numeric and/or alphanumeric keypad)) that isseparate (e.g., that is not physically integrated into the computersystem; that does not power on (or off) when the computer system ispowered on (or off)) from the computer system; and In some embodiments,the computer system is in communication (e.g., wireless communication)with the second electronic lock. Displaying representations of multipleelectronic locks and their state provides the user with visual feedbackabout the locks with which the computer system is in communication andthe state of the home automation system.

In some embodiments, the user account lock user interface (e.g., 818,842) includes a code (e.g., 822 a, 846 b) (e.g., a numerical code, analphabetical code, an alphanumerical code) associated with (e.g., of,corresponding to) the first account, wherein a respective electroniclock (e.g., the first electronic lock and/or the second electronic lock)is configured to unlock, based the respective electronic lock beingconfigured to be operated by (e.g., unlocked by) the first account(e.g., using credentials of the first account, using credentials of thesecond account), upon receipt of (e.g., entry at a keypad of therespective electronic lock of) the code. In some embodiments, theaccount lock user interface includes a code that can be used to unlocklocks enabled to be controlled by the first account. Displaying a codeassociated with the first account provides the user with visual feedbackabout the configuration of the first account.

In some embodiments, the computer system (e.g., 600) detects selection(e.g., 850 j) of (e.g., a tap gestures on, a press-and-hold gesture on)the code (e.g., 822 a, 846 b) associated with the first account. Inresponse to detecting selection of the code associated with the firstaccount, the computer system (e.g., 600) initiates a process (e.g., asshown in FIG. 8H) for transmitting the code (e.g., via instant messageand/or email) to a recipient (e.g., to a user corresponding to the firstaccount). In some embodiments, initiating the process for transmittingthe code to the recipient includes displaying selectable user interfaceobjects for a plurality of users, including the recipient. The computersystem receives selection of a user interface object corresponding tothe recipient and, in response, displays a draft instant message thatincludes the code. In response to detecting a send request (e.g., tapinput on a send button of the draft instant message), the computersystem transmits the code to the recipient via instant message.Initiating a process for transmitting the code in response to selectionof the code enables the computer system to quickly and accurately sharethe code with a recipient (e.g., without the need for the user toseparately access a messaging application and to enter the code).

In some embodiments, the first account corresponds to a user account ofthe computer system (e.g., 600) (e.g., the first account belongs to theuser that is signed into the computer system) and an electronic wallet(e.g., an electronic wallet user interface) of the computer systemincludes a visual representation (e.g., a card in the electronic walletand/or representing a key) of the first account. Displaying a visualrepresentation of the first account as part of an electronic walletprovides the user with feedback about the state of the computer systemand that it includes the key.

In some embodiments, the computer system (e.g., 600) transmits, to thefirst electronic lock (and/or a second electronic lock) via short-rangecommunication (e.g., via NFC, WiFi, and/or UWB), credentials of thefirst account to unlock the first electronic lock (and/or the secondelectronic lock). In some embodiments, the first account can be used towirelessly unlock locks of the home automation system configured to beunlocked using credentials of the first account. In some embodiments,communicating via short-range communication includes communicating usinga short-range communication protocol.

In some embodiments, while displaying the user account lock userinterface (e.g., 818, 842) corresponding to a first account, thecomputer system (e.g., 600) receives second input (e.g., 850 g) (e.g., atap input). In response to receiving the second input: in accordancewith a determination that the second input corresponds to selection ofthe first status object corresponding to the first electronic lock, thecomputer system (e.g., 600) changes (e.g., from configured to unlock tonot configured to unlock; from not configured to unlock to configured tounlock) whether the first electronic lock is configured to unlock usingcredentials (e.g., a pin code entered at the first electronic lock by auser and/or a credential transmitted to the first electronic lock by thecomputer system) of the first account (e.g., without changing whetherthe second electronic lock is configured to unlock using credentials ofthe first account) and in accordance with a determination that thesecond input corresponds to selection of the second status objectcorresponding to the second electronic lock, the computer system (e.g.,600) changes (e.g., from configured to unlock to not configured tounlock; from not configured to unlock to configured to unlock) whetherthe second electronic lock is configured to unlock using credentials(e.g., a pin code entered at the second electronic lock by a user and/ora credential transmitted to the second electronic lock by the computersystem) of the first account (e.g., without changing whether the firstelectronic lock is configured to unlock using credentials of the firstaccount). In some embodiments, the first and/or second status objectchanges to indicated whether the respective electronic lock isconfigured to be unlocked using credentials of the first account.Receiving user input to change whether the first or second electroniclock is configured to unlock using credentials of the first accountenables the computer system control the home automation system, therebyallowing the user to secure particular electronic locks and/or allowcertain users access to other electronic locks.

In some embodiments, the user account lock user interface (e.g., 818,842) includes a code change user interface object. While displaying theuser account lock user interface (e.g., 818, 842) corresponding to afirst account, the computer system receives third input (e.g., 850 h)(e.g., a tap input). In response to receiving the third input and inaccordance with a determination that the third input corresponds toselection of the code change user interface object (e.g., 822 b), thecomputer system (e.g., 600) initiates a process to set (e.g., change)the code associated with the first account for operating a plurality ofelectronic locks. In some embodiments, initiating the process to changethe code associated with the first account includes displaying a keypad(e.g., a numerical keypad) for receiving entry of a replacement code. Insome embodiments, changing the code associated with the first accountchanges the code for all electronic locks of the home automation systemfor the first account. Changing the code for the first account andhaving that change apply to multiple electronic locks of the homeautomation system allows the computer system to reconfigure multipleelectronic locks for that user without the need to receive user inputsspecific to each electronic lock of the home automation system to setthe same code, thereby reducing the number of inputs required.

In some embodiments, the first electronic lock and the second electroniclock are a part of a home automation system and wherein one or moreusers of the home automation system are designated as residents of(e.g., are a resident of a home corresponding to) the home automationsystem and one or more users of the home automation system aredesignated as guests of (e.g., are guests in the home corresponding to)the home automation system. In some embodiments, accounts of residentshave access to additional and/or more features of the home automationsystem as compared to accounts of guests. Designating users of the homeautomation system as residents and guests enables the computer system toconfigure the home automation system with different levels of access fordifferent types of users, thereby simplifying configuration of the homeautomation system and making the system more secure.

In some embodiments, the computer system (e.g., 600) concurrentlydisplays, via the display generation component (e.g., as part of theaccount user interface):

an indication (e.g., 870) (e.g., a group heading, below which residentsare listed) that a second user of the home automation system is aresident of (e.g., is a resident of a home corresponding to) the homeautomation system without displaying a code of a second accountassociated with the second user, an indication (e.g., 872) (e.g., agroup heading, below which guests are listed) that a third user of thehome automation system is a guest in (e.g., is a guest in the homecorresponding to) the home automation system, and a code (e.g., 873) ofa third account associated with the third user. In some embodiments,respective codes of guests are displayed while respective codes ofresidents are not displayed. In some embodiments, one or more users(e.g., each user) of the home automation system is associated with arespective code (e.g., a numerical code, an alphabetical code, analphanumerical code), wherein a respective electronic lock (e.g., thefirst electronic lock and/or the second electronic lock) is configuredto unlock, based the respective electronic lock being configured to beoperated by (e.g., unlocked by) the respective account (e.g., usingcredentials of the first/second/third account), upon receipt of (e.g.,entry at a keypad of the respective electronic lock of) the code. Insome embodiments, the computer system also includes an indication ofwhether the first account is a resident or guest of the home automationsystem. Displaying codes for guests without displaying codes forresidents enables the computer system to provide the user with visualfeedback about the state of the home automation system for guest userswho may otherwise have limited access to learning their code whilemaintaining the security of the home automation system by not displayingcodes for residents who may have access (e.g., through their owndevices) to their respective codes.

In some embodiments, the computer system (e.g., 600) concurrentlydisplays, via the display generation component (e.g., as part of theaccount user interface) indications of one or more resident users (e.g.,854 a-854 c) of the home automation system (e.g., without displayingrespective codes of the one or more resident users) and a guest userinterface object (e.g., 854 d) (e.g., without displaying individualindications for (e.g., names of) guests of the home automation systemand/or without displaying respective codes for the guests). The computersystem (e.g., 600) receives selection of the guest user interfaceobject. In response to receiving selection of the guest user interfaceobject, the computer system (e.g., 600) concurrently displays, via thedisplay generation component: an indication of a first guest of the homeautomation system and a code associated with an account of the firstguest, and an indication of a second guest of the home automation systemand a code associated with an account of the second guest. In someembodiments, guests of the home automation system are each associatedwith a respective code (e.g., a numerical code, an alphabetical code, analphanumerical code), wherein a respective electronic lock (e.g., thefirst electronic lock and/or the second electronic lock) is configuredto unlock, based the respective electronic lock being configured to beoperated by (e.g., unlocked by) the respective guest account (e.g.,using credentials of the guest account), upon receipt of (e.g., entry ata keypad of the respective electronic lock of) the code. In someembodiments, guests of the home automation system are grouped together(e.g., a single UI object to access the list of guests) and residentsare grouped together (e.g., displayed as part of a list, in anothersection of the UI). In some embodiments, displaying a guest userinterface object that displays the guests of the home automation networkenables the computer system to provide the user with visual feedbackabout the type of user information being displayed (e.g., whether theusers displayed are residents or guests). Displaying the respectivecodes of the guests provides the user with visual feedback about thestate of the home automation system.

In some embodiments, the first electronic lock and the second electroniclock are a part of a home automation system (and, optionally, whereinthe account user interface includes indications of a plurality of users(e.g., residents and/or guests) of the home automation system). Whiledisplaying, via the display generation component, the account userinterface, the computer system (e.g., 600) receives fourth input (e.g.,a tap input). In response to receiving the fourth input and inaccordance with a determination that the fourth input is directed to adisable object (e.g., 870 a-870 c, 872 a-872 c) corresponding to a firstuser (corresponding to the first account) of the plurality of users, thecomputer system (e.g., 600) configures the first electronic lock and thesecond electronic lock to not be operated by (e.g., unlocked by)credentials of the first account associated with the first user (e.g.,without configuring the first and second electronic locks to not beoperated by credentials of a second account associated with a seconduser). In some embodiments, in response to receiving the fourth inputand in accordance with a determination that the fourth input is directedto a disable object corresponding to a second user of the plurality ofusers, configuring the first electronic lock and the second electroniclock to not be operated by (e.g., unlocked by) credentials of a secondaccount associated with the second user (e.g., without configuring thefirst and second electronic locks to not be operated by credentials ofthe first account associated with the first user). Enabling the computersystem to disable an account (e.g., so that the code of the account doesnot operate the electronic locks of the home automation system and/or sothat the account cannot be used to wirelessly (e.g., via NFC, viaBluetooth, via UWB) operate the electronic locks of the home automationsystem) allows a user of the computer system to secure the homeautomation system by ending the access provided by the account.

In some embodiments, the user account lock user interface (e.g., 842)includes an option (e.g., 842 a) (e.g., a text field) for naming (e.g.,entering a name for, changing an existing name of) the first account. Insome embodiments, the computer system (e.g., 600) receives one or moreinputs (e.g., selection of the text field, entry of a new name, and/orselection of a completion UI object indicating the user has finishedentering a new name for the first account). In response to receiving theone or more inputs, naming the first account. Receiving inputscorresponding to a name and associating the first account with the nameallows the computer system to more readily provide the user withinformation about the first account by using the name, thereby improvingthe man-machine interface.

In some embodiments, subsequent to (e.g., in response to) changingaccess of the first account (e.g., with respect to the home automationsystem), causing a notification (e.g., 836) to be sent (e.g.,transmitting the notification and/or requesting that an externalelectronic device transmit the notification) to one or more othercomputer systems (other than the computer system and/or of a user of thehome automation system) (e.g., transmitting the notifications to the oneor more other computer systems and/or providing information to a secondcomputer system to transmit the notifications to the one or more othercomputer system) associated with the first account (e.g., wherein thenotification indicates the change in access). Causing a notification tobe sent to one or more other computer systems associated with the firstaccount provides the users of the computer systems with the change inthe access of the first account.

In some embodiments, the change in access of the first account is achange to the code associated with the first account. In someembodiments, the change in access of the first account is a change tothe electronic locks (e.g., lock added and/or lock removed) configuredto be operated by (e.g., unlocked by) the first account. In someembodiments, the change in access of the first account is a request todisable the first account (e.g., via selection of disable objectcorresponding to a first user). In some embodiments, notifications ofchanges in access are sent when there is a change in access to aresident and are not sent when there is a change in access to a guest.

In some embodiments, notifications of changes in access can be disable(e.g., regardless of whether the user is a guest or resident). In someembodiments, notifications regarding the status (e.g., locked, unlocked)of respective (and/or all) electronic locks can be enabled and disabled.In some embodiments, the computer system configures the home automationsystem to send a notification to the computer system when credentials ofan account (e.g., the first account) are used (e.g., via a code entry atthe electronic lock) to unlock an electronic lock (e.g., thenotification identifying the corresponding user and the correspondingelectronic lock that was unlocked). In some embodiments, the computersystem can configured disable the home automation system from sendingnotifications when credentials of an account (e.g., the first account)are used (e.g., via a code entry at the electronic lock) to unlock anelectronic lock.

Note that details of the processes described above with respect tomethod 900 (e.g., FIG. 9 ) are also applicable in an analogous manner tothe methods described above. For example, method 700 optionally includesone or more of the characteristics of the various methods describedabove with reference to method 900. For example, the electronic lock ofmethod 700 is the same as the first or second electronic lock of method900. For another example, the computer system of method 700 is the sameas the computer system of method 900. For another example, the firstaccount of method 700 is the same as the first account of method 900.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

As described above, one aspect of the present technology is thegathering and use of data available from various sources to improve auser's ability to manage lock accessory devices of a home automationsystem. The present disclosure contemplates that in some instances, thisgathered data may include personal information data that uniquelyidentifies or can be used to contact or locate a specific person. Suchpersonal information data can include demographic data, location-baseddata, telephone numbers, email addresses, twitter IDs, home addresses,data or records relating to a user's health or level of fitness (e.g.,vital signs measurements, medication information, and/or exerciseinformation), date of birth, or any other identifying or personalinformation.

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. For example, the personal information data can be used toprovide access to one or more lock accessory devices. Accordingly, useof such personal information data enables users to have calculatedcontrol of other individuals and/or users that have access to the one ormore lock accessory devices. Further, other uses for personalinformation data that benefit the user are also contemplated by thepresent disclosure.

The present disclosure contemplates that the entities responsible forthe collection, analysis, disclosure, transfer, storage, or other use ofsuch personal information data will comply with well-established privacypolicies and/or privacy practices. In particular, such entities shouldimplement and consistently use privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining personal information data private andsecure. Such policies should be easily accessible by users, and shouldbe updated as the collection and/or use of data changes. Personalinformation from users should be collected for legitimate and reasonableuses of the entity and not shared or sold outside of those legitimateuses. Further, such collection/sharing should occur after receiving theinformed consent of the users. Additionally, such entities shouldconsider taking any needed steps for safeguarding and securing access tosuch personal information data and ensuring that others with access tothe personal information data adhere to their privacy policies andprocedures. Further, such entities can subject themselves to evaluationby third parties to certify their adherence to widely accepted privacypolicies and practices. In addition, policies and practices should beadapted for the particular types of personal information data beingcollected and/or accessed and adapted to applicable laws and standards,including jurisdiction-specific considerations. For instance, in the US,collection of or access to certain health data may be governed byfederal and/or state laws, such as the Health Insurance Portability andAccountability Act (HIPAA); whereas health data in other countries maybe subject to other regulations and policies and should be handledaccordingly. Hence different privacy practices should be maintained fordifferent personal data types in each country.

Despite the foregoing, the present disclosure also contemplatesembodiments in which users selectively block the use of, or access to,personal information data. That is, the present disclosure contemplatesthat hardware and/or software elements can be provided to prevent orblock access to such personal information data. For example, in the caseof managing access to lock accessory devices of a home automationsystem, the present technology can be configured to allow users toselect to “opt in” or “opt out” of participation in the collection ofpersonal information data during registration for services or anytimethereafter. In another example, users can select not to acceptauthorization for access to one or more lock accessory devices of thehome automation system. In addition to providing “opt in” and “opt out”options, the present disclosure contemplates providing notificationsrelating to the access or use of personal information. For instance, auser may be notified upon downloading an app that their personalinformation data will be accessed and then reminded again just beforepersonal information data is accessed by the app.

Moreover, it is the intent of the present disclosure that personalinformation data should be managed and handled in a way to minimizerisks of unintentional or unauthorized access or use. Risk can beminimized by limiting the collection of data and deleting data once itis no longer needed. In addition, and when applicable, including incertain health related applications, data de-identification can be usedto protect a user's privacy. De-identification may be facilitated, whenappropriate, by removing specific identifiers (e.g., date of birth,etc.), controlling the amount or specificity of data stored (e.g.,collecting location data a city level rather than at an address level),controlling how data is stored (e.g., aggregating data across users),and/or other methods.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedembodiments, the present disclosure also contemplates that the variousembodiments can also be implemented without the need for accessing suchpersonal information data. That is, the various embodiments of thepresent technology are not rendered inoperable due to the lack of all ora portion of such personal information data. For example, anadministrator user of the home automation system can provide access toone or more lock accessory devices to users based on non-personalinformation data or a bare minimum amount of personal information, suchas the content being requested by the device associated with a user orpublicly available information.

What is claimed is:
 1. A computer system configured to communicate witha display generation component and one or more input devices,comprising: one or more processors; and memory storing one or moreprograms configured to be executed by the one or more processors, theone or more programs including instructions for: displaying, via thedisplay generation component, an account user interface that includes auser account lock object; while displaying the user account lock object,receiving, via the one or more input devices, a first inputcorresponding to selection of the user account lock object; and inresponse to receiving the first input, displaying, via the displaygeneration component, a user account lock user interface correspondingto a first account, wherein the user account lock user interfaceincludes concurrent display of: a first electronic lock objectcorresponding to a first electronic lock that is separate from thecomputer system; a first status object that indicates whether the firstelectronic lock is configured to unlock using credentials of the firstaccount; a second electronic lock object corresponding to a secondelectronic lock that is separate from the computer system; and a secondstatus object that indicates whether the second electronic lock isconfigured to unlock using credentials of the first account.
 2. Thecomputer system of claim 1, wherein the user account lock user interfaceincludes a code associated with the first account, wherein a respectiveelectronic lock is configured to unlock, based the respective electroniclock being configured to be operated by the first account, upon receiptof the code.
 3. The computer system of claim 2, wherein the one or moreprograms further include instructions for: detecting selection of thecode associated with the first account; and in response to detectingselection of the code associated with the first account, initiating aprocess for transmitting the code to a recipient.
 4. The computer systemof claim 2, wherein: the first account corresponds to a user account ofthe computer system; and an electronic wallet of the computer systemincludes a visual representation of the first account.
 5. The computersystem of claim 1, wherein the one or more programs further includeinstructions for: transmitting, to the first electronic lock viashort-range communication, credentials of the first account to unlockthe first electronic lock.
 6. The computer system of claim 1, whereinthe one or more programs further include instructions for: whiledisplaying the user account lock user interface corresponding to a firstaccount: receiving second input; and in response to receiving the secondinput: in accordance with a determination that the second inputcorresponds to selection of the first status object corresponding to thefirst electronic lock, changing whether the first electronic lock isconfigured to unlock using credentials of the first account; and inaccordance with a determination that the second input corresponds toselection of the second status object corresponding to the secondelectronic lock, changing whether the second electronic lock isconfigured to unlock using credentials of the first account.
 7. Thecomputer system of claim 1, wherein the user account lock user interfaceincludes a code change user interface object, wherein the one or moreprograms further include instructions for: while displaying the useraccount lock user interface corresponding to a first account: receivingthird input; and in response to receiving the third input and inaccordance with a determination that the third input corresponds toselection of the code change user interface object, initiating a processto set the code associated with the first account for operating aplurality of electronic locks.
 8. The computer system of claim 1,wherein the first electronic lock and the second electronic lock are apart of a home automation system and wherein one or more users of thehome automation system are designated as residents of the homeautomation system and one or more users of the home automation systemare designated as guests of the home automation system.
 9. The computersystem of claim 8, wherein the one or more programs further includeinstructions for: concurrently displaying, via the display generationcomponent: an indication that a second user of the home automationsystem is a resident of the home automation system without displaying acode of a second account associated with the second user; an indicationthat a third user of the home automation system is a guest in the homeautomation system; and a code of a third account associated with thethird user.
 10. The computer system of claim 8, wherein the one or moreprograms further include instructions for: concurrently displaying, viathe display generation component: indications of one or more residentusers of the home automation system; and a guest user interface object;receiving selection of the guest user interface object; and in responseto receiving selection of the guest user interface object, concurrentlydisplaying, via the display generation component: an indication of afirst guest of the home automation system and a code associated with anaccount of the first guest; and an indication of a second guest of thehome automation system and a code associated with an account of thesecond guest.
 11. The computer system of claim 1, wherein the firstelectronic lock and the second electronic lock are a part of a homeautomation system, wherein the one or more programs further includeinstructions for: while displaying, via the display generationcomponent, the account user interface, receiving fourth input; and inresponse to receiving the fourth input and in accordance with adetermination that the fourth input is directed to a disable objectcorresponding to a first user of the plurality of users, configuring thefirst electronic lock and the second electronic lock to not be operatedby credentials of the first account associated with the first user. 12.The computer system of claim 1, wherein the user account lock userinterface includes an option for naming the first account, wherein theone or more programs further include instructions for: receiving one ormore inputs; and in response to receiving the one or more inputs, namingthe first account.
 13. The computer system of claim 1, wherein the oneor more programs further include instructions for: subsequent tochanging access of the first account, causing a notification to be sentto one or more other computer systems associated with the first account.14. A non-transitory computer-readable storage medium storing one ormore programs configured to be executed by one or more processors of acomputer system that is in communication with a display generationcomponent and one or more input devices, the one or more programsincluding instructions for: displaying, via the display generationcomponent, an account user interface that includes a user account lockobject; while displaying the user account lock object, receiving, viathe one or more input devices, a first input corresponding to selectionof the user account lock object; and in response to receiving the firstinput, displaying, via the display generation component, a user accountlock user interface corresponding to a first account, wherein the useraccount lock user interface includes concurrent display of: a firstelectronic lock object corresponding to a first electronic lock that isseparate from the computer system; a first status object that indicateswhether the first electronic lock is configured to unlock usingcredentials of the first account; a second electronic lock objectcorresponding to a second electronic lock that is separate from thecomputer system; and a second status object that indicates whether thesecond electronic lock is configured to unlock using credentials of thefirst account.
 15. A method, comprising: at a computer system that is incommunication with a display generation component and one or more inputdevices: displaying, via the display generation component, an accountuser interface that includes a user account lock object; whiledisplaying the user account lock object, receiving, via the one or moreinput devices, a first input corresponding to selection of the useraccount lock object; and in response to receiving the first input,displaying, via the display generation component, a user account lockuser interface corresponding to a first account, wherein the useraccount lock user interface includes concurrent display of: a firstelectronic lock object corresponding to a first electronic lock that isseparate from the computer system; a first status object that indicateswhether the first electronic lock is configured to unlock usingcredentials of the first account; a second electronic lock objectcorresponding to a second electronic lock that is separate from thecomputer system; and a second status object that indicates whether thesecond electronic lock is configured to unlock using credentials of thefirst account.